Plugging a pseudo-memory leak

A

Adam Atlas

I have a program that seemed to be leaking memory, but after
debugging, it seemed it just wasn't getting around to collecting the
objects in question often enough. The objects are very long-lived, so
they probably end up in generation 2, and don't get collected for a
long time. Is there any way I can force collection of these objects? I
know in Python 2.5 there's gc.collect(2), but I want to keep it
compatible with previous versions of Python.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,471
Messages
2,571,823
Members
48,797
Latest member
PeterSimpson
Top