A painful, but effective way is to get a rough idea of what might be
leaking and then go disable code in the thing that you think is leaking
in large sections... I know this isn't very helpful, but it's true.
Andy McKay wrote:
>
> Does anyone have advice for tracking (apparent) memory leaks other than
> sitting watching DebugInfo?
>
> Cheers.
> --
> Andy McKay.
>
> _______________________________________________
> Zope-Dev maillist - [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope )
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
