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 on unpickling bogus data #69911
Comments
New tests added in bpo-23914 exposed memory leak on unpickling TUPLE1..TUPLE3 opcodes with insufficient stack. Proposed patch fixes the leak. |
$ ./python -m test.regrtest -R 3:3 -m test_bad_stack test_pickle
[1/1] test_pickle
beginning 6 repetitions
123456
......
test_pickle leaked [20, 20, 20] references, sum=60
test_pickle leaked [12, 14, 14] memory blocks, sum=40
1 test failed:
test_pickle |
Oh... I didn't notice that you wrote a patch :-) I started to write a similar patch: see attached pickle.patch. |
I reviewed load_counted_tuple_leak.patch. Forget my patch, Serhiy's patch is better. |
You patch is just the first version of my patch. :-) But tests are crashed with it. |
New changeset c85eca74f3a5 by Serhiy Storchaka in branch '3.4': New changeset 88ad2b8480b1 by Serhiy Storchaka in branch '3.5': New changeset 935debb548a3 by Serhiy Storchaka in branch 'default': New changeset 9a4db1ac5e10 by Serhiy Storchaka in branch '2.7': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: