On Wed, Sep 10, 2008 at 2:05 PM, James Cameron <[EMAIL PROTECTED]> wrote: > I had a few hours look at the second largest process, the journal > activity, on Joyride 2412. > > Then I used gdb to generate-core-file and wander through the heap memory > to get an idea of what it might contain. I did not make a complete > analysis. I need to learn more about the heap structures before I do > so.
Wonder if this is what people familiar with python internals do? Haven't tried myself. > But I did notice one odd thing that I wasn't fully aware of until now > ... the byte-code of the built-in modules was present, complete with doc > strings ... for example; Yes, we are aware of this one and have a fix on the line: https://bugzilla.redhat.com/show_bug.cgi?id=460334 There has been a thread recently on devel or sugar ml about it. If you could help us quantify how much this could help, it would be much appreciated. > Has anyone got an idea of how to measure the heap by usage? Not from outside python, but from inside we are using heapy: http://guppy-pe.sourceforge.net/ Thanks, Tomeu _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
