[Zope-dev] Memory leak (2)

[Andy McKay]

> It's not covered by the data output into the -M log.  Objects can leak
> without requests hanging or taking a long time.  But you might be able to
> turn on profiling (set the PROFILE_PUBLISHER env var to a filename and
> restart Zope) on a *test* box (do not do it in production, it drastically
> effects performance), and look at the profile output.  If the memory loss
is
> severe, it might help to investigate the methods that have the largest
> "ncalls" value (the most frequently called methods).  That said, there's
no
> globally easy way to diagnose a memory leak.  It's a matter of exclusion.

Well there goes that idea. Forgot about profiling, thanks.
--
  Andy McKay.