← 返回首页
gh-91404: Revert "bpo-23689: re module, fix memory leak when a match is terminated by a signal or memory allocation failure (GH-32283)" · Pull Request #93559 · python/cpython · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Resetting focus

gh-91404: Revert "bpo-23689: re module, fix memory leak when a match is terminated by a signal or memory allocation failure (GH-32283)"#93559

Closed
ghost wants to merge 2 commits into
mainfrom
unknown repository
Closed

gh-91404: Revert "bpo-23689: re module, fix memory leak when a match is terminated by a signal or memory allocation failure (GH-32283)"#93559
ghost wants to merge 2 commits into
mainfrom
unknown repository

Conversation

ghost commented Jun 7, 2022

Copy link
Copy Markdown

In nesting repeats, a repeat context may have multiple active existences at the same time.
So 6e3eee5's method is wrong.

…ted by a signal or memory allocation failure (GH-32283)" This reverts commit 6e3eee5.

gpshead commented Jun 15, 2022

Copy link
Copy Markdown
Member

I created a similar PR as I hadn't seen this one mentioned on the #91404 issue.

At a quick glance without diving deep to compare diffs, the MAGIC constants are not being updated by this PR while I decided to do that in mine.

ghost closed this Jun 16, 2022
This pull request was closed.
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Footer

© 2026 GitHub, Inc.