[EMAIL PROTECTED] writes: > I have a rather large python application (uses around 40MB of memory to > start) that gradually chews up memory over many hours. I've done a > little googling around, but it looks like I'm faced with prowling > through the gc.get_objects() myself. I need a tool to identify where > the memory is going. It might even be a leak in a DLL, so maybe a pure > python profiler isn't the best, although it would certainly help > localize the problem.
One is being written as part of Google's Summer Of Code program. Cheers, mwh -- Java sucks. [...] Java on TV set top boxes will suck so hard it might well inhale people from off their sofa until their heads get wedged in the card slots. --- Jon Rabone, ucam.chat -- http://mail.python.org/mailman/listinfo/python-list
