A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/132985.html below:

[Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__]

[Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__] [Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__]Chris Angelico rosuav at gmail.com
Sat Mar 8 11:39:38 CET 2014 
On Sat, Mar 8, 2014 at 9:06 PM, Victor Stinner <victor.stinner at gmail.com> wrote:
> And MyObject is not destroyed which is an obvious memory leak, beause
> there is no more explicit reference to it.

And it doesn't seem to be getting put into gc.garbage, either, which
is probably worth mentioning. You have __del__ in there, so it's
entirely possible it would get dropped into the garbage rather than
actually disposed of, but I added a print(gc.garbage) after
gc.collect() and it showed empty.

ChrisA
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4