[Tiny Feature] Re-enable ASan leak detection after fixing #266/#275 #286
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
john/McRogueFace#286
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
The ASan test suite currently runs with
detect_leaks=0because CPython has intentional lifetime leaks (interned strings, type objects, small int cache) that flood LeakSanitizer output. However, this also suppresses detection of real leaks like #266 (UIEntity self-reference cycle) and #275 (unbalanced Py_INCREF in entity init).Proposal
After fixing #266 and #275:
detect_leaks=1inASAN_OPTIONSsanitizers/asan.supp)Related