See http://dev.laptop.org/ticket/10386 for details. The sugar-session
process in 10.1.2 grows slowly...
There's some form of leak somewhere. Maybe we are triggerin a real
python leak, maybe we have reference loops. How do we trace this?
Tomeu wrote some instructions here:
http://wiki.laptop.org/go/Memory_leak_testing
http://wiki.sugarlabs.org/go/Development_Team/Memory/Leak_testing (mirror)
that might be of use to you.
Also, it looks like guppy is now available directly from Fedora, packaged under
the name "python-guppy".
Michael
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
