Repository navigation
gh-126491: Revert "GH-126491: Lower heap size limit with faster marking (GH-127519)" - #127770
Merged
encukou merged 1 commit intoDec 10, 2024
Merged
encukou merged 1 commit into
encukou merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
…ythonGH-127519)" This reverts commit 023b7d2, which introduced a refleak.
srinivasreddy
pushed a commit
to srinivasreddy/cpython
that referenced
this pull request
Jan 8, 2025
…faster marking (pythonGH-127519)" (pythonGH-127770) Revert "pythonGH-126491: Lower heap size limit with faster marking (pythonGH-127519)" This reverts commit 023b7d2, which introduced a refleak.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This reverts commit 023b7d2, which introduced a refleak in test_import.
Per PEP 11 break should be fixed or reverted immediately. I don't immediately see the problem, though. (Perhaps it's just a test issue?)