I use it something like: with memoryTracker(): # code suspected of leaking
You can also play around with it on the local development server (hopefully the leak reproduces there). And you could try using other methods from objgraph to understand the source of the leak (http://mg.pov.lt/objgraph/), though it probably won't be easy :( Attila -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/50ad881d-7128-4f70-9193-6bb1bb3142d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
