[Python-Dev] Python GC/type()/weakref mystery (original) (raw)
Aahz aahz at pythoncraft.com
Thu Mar 18 12🔞32 EST 2004
- Previous message: [Python-Dev] Python GC/type()/weakref mystery
- Next message: [Python-Dev] Python GC/type()/weakref mystery
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Mar 18, 2004, Kevin Jacobs wrote:
Varying the value of N also results in strange results: for i in range(6): leaktest(10**i, newtype) Produces: Leak detected (N=1, 1 new objects) Leak detected (N=10, 9 new objects) Leak detected (N=100, 90 new objects) Leak detected (N=1000, 78 new objects) Leak detected (N=10000, 9 new objects) Leak detected (N=100000, 8 new objects)
This looks to me like standard boundary conditions for GC; GC normally only gets provoked when more than gc.get_threshold() objects have been created than deleted. What makes you think something unusual is happening?
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
"usenet imitates usenet" --Darkhawk
- Previous message: [Python-Dev] Python GC/type()/weakref mystery
- Next message: [Python-Dev] Python GC/type()/weakref mystery
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]