Skip to content

Navigation Menu

Sign in
Appearance settings

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

Provide feedback

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

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Incremental GC double-counts work done during the marking phase #141890

Copy link
Copy link
Open
Open
Incremental GC double-counts work done during the marking phase#141890
Copy link
Assignees
brandtbucher
Labels
3.14bugs and security fixesbugs and security fixes3.15pre-release feature fixes, bugs and security fixespre-release feature fixes, bugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
@brandtbucher

Description

@brandtbucher
brandtbucher
opened on Nov 24, 2025
Issue body actions

Bug report

Both mark_at_start and gc_collect_increment (its caller) decrement work_to_do by the number of objects marked. This can result in incremental collections being delayed longer than expected... I think in extreme situations, collection could be delayed indefinitely, resulting in leaks.

The fix is simple, just remove one of the decrements.

Linked PRs

Reactions are currently unavailable

Metadata

Metadata

Assignees

Labels

3.14bugs and security fixesbugs and security fixes3.15pre-release feature fixes, bugs and security fixespre-release feature fixes, bugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    Morty Proxy This is a proxified and sanitized view of the page, visit original site.