HTTPS: memory leakage

[Martin v. Löwis]

paolo at prosa.it (Paolo Andreetto) writes:

> Does it depend on the code or is there any problem in the system?

I recommend to run gc.collect() at each iteration. If you want to know
more details, you should activate gc.DEBUG_STATS before the loop.
After each collect invocation, make sure gc.garbage is empty.

If you find that gc does indeed collect objects, you can use
gc.DEBUG_SAVEALL to put the objects into gc.garbage instead of
collecting them.

If you find that memory consumption still goes up even though GC runs
often, and even though gc.garbage does not grow, you'll need more
powerful analysis tools.

Regards,
Martin