On 8 October 2010 03:34, Martin Langhoff <martin.langh...@gmail.com> wrote:
> 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? > This post seems pretty good [1]. It cites a tool that creates an object graph that visually represents what is happening in memory.[2] [1] http://www.lshift.net/blog/2008/11/14/tracing-python-memory-leaks [2] http://mg.pov.lt/blog/python-object-graphs.html
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
