Is there any way to manually remove an object which the garbage collection refuses to get rid of even when I call gc.collect()
? Working in Python 3.0
相关问题
- how to define constructor for Python's new Nam
- streaming md5sum of contents of a large remote tar
- How to get the background from multiple images by
- Evil ctypes hack in python
- Correctly parse PDF paragraphs with Python
Per the docs,
gc.get_referrers(thatobject)
will tell you why the object is still alive (do it right after agc.collect()
to make sure the undesired "liveness" is gonna be persistent). After that, it's somehow of a black art;-). You'll often find that some of the referrers are lists (so WHY is that list referring tothatobject
? you can.remove
it in an emergency mode, but making the normal code sound is better...), and, even more often,dict
s (many of whose may be__dict__
s of some class instance or other -- often not trivial to find out which one... again, brute-force removal is sometimes an expedient emergency solution, but never a sustainable long-range one!-).It depends on what your Python is running on. Here's good article that explains the details
Quoting:
In current releases of CPython, each new assignment to x inside the loop will release the previously allocated resource. Using GC, this is not guaranteed. If you want to write code that will work with any Python implementation, you should explicitly close the resource; this will work regardless of GC:
If the GC is refusing to destroy it, it's because you have a reference to it somewhere. Get rid of the reference and it will (eventually) go. For example:
Keep in mind that GC may not necessarily destroy your object unless it needs to.
If your object is holding resources not under the management of Python (e.g., some trickery with C code called from Python), the object should provide a resource release call so you can do it when you want rather than when Python decides.
del
OrNone
are your only friends