Skip to content

[WIP] bpo-35502: Fix memory leak in xml.etree iterparse() #11169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

[WIP] bpo-35502: Fix memory leak in xml.etree iterparse() #11169

wants to merge 1 commit into from

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Dec 14, 2018 •
edited by bedevere-bot
Loading

@ZackerySpytz
Copy link
Contributor

The issue number is wrong.

@serhiy-storchaka
Copy link
Member

serhiy-storchaka commented Dec 14, 2018 •
edited by bedevere-bot
Loading

Is it for bpo-35502? I afraid that this change would reintroduce a performance regression fixed in bpo-25638.

@vstinner
Copy link
Member Author

This change is too complex for the fixed bug. I have a simpler fix.

@vstinner vstinner closed this Dec 18, 2018
@vstinner vstinner deleted the etree branch December 18, 2018 11:13
@vstinner vstinner changed the title [WIP] bpo-35257: Fix memory leak in xml.etree iterparse() [WIP] bpo-35502: Fix memory leak in xml.etree iterparse() Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@serhiy-storchaka serhiy-storchaka Awaiting requested review from serhiy-storchaka

Assignees
No one assigned
Labels
awaiting merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@vstinner @ZackerySpytz @serhiy-storchaka @the-knights-who-say-ni @bedevere-bot