-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Memory leak related to return in try/finally #760
Comments
@dagss changed priority from |
@dagss changed description from
to
commented This bug has apparently been in Cython for some time. With code like
then The fix is of course easy; assign This is another thing that longer-term would be solved by control flow analysis. |
scoder commented Yes, starting off with None was my first thought, too. And I find it ok as a quick fix for 0.11. Correct code first. |
@dagss changed owner to Fix attached, this can be closed when I get to push it or someone else applies it. |
@dagss changed owner from |
scoder changed resolution to I assume that this can be fixed now that the patch is in. |
tryfinally.pyx
has a genuine leak reported by the refcount nanny:At 2009-02-20T00:50:29Z @dagss added attachment 200.diff
Migrated from http://trac.cython.org/ticket/200
The text was updated successfully, but these errors were encountered: