finding memory leak in edgewall trac 0.11

[rupert.thurner]

what would be a good means of finding where the 0.11 version of
edgewall trac uses excessive memory. see
http://groups.google.com/group/trac-...16e519da54f16b
for some details, where jonas suggested
http://wingolog.org/archives/2007/11...n-applications
as reading.

tiran already gave some hints on http://bugs.python.org/issue1871, but
also suggested to ask the general mailing list:

Do you have classes with a __del__ method which may create reference
cycles? The GC can't break cycles when a __del__ method is involved.

Are you keeping references to tracebacks, exception objects (except
Exception, err) or frames (sys._getframe())

many thanks,

rupert.

[Christian Heimes]

rupert.thurner wrote:

what would be a good means of finding where the 0.11 version of
edgewall trac uses excessive memory. see
http://groups.google.com/group/trac-...16e519da54f16b
for some details, where jonas suggested
http://wingolog.org/archives/2007/11...n-applications
as reading.

tiran already gave some hints on http://bugs.python.org/issue1871, but
also suggested to ask the general mailing list:

Do you have classes with a __del__ method which may create reference
cycles? The GC can't break cycles when a __del__ method is involved.

Are you keeping references to tracebacks, exception objects (except
Exception, err) or frames (sys._getframe())

I forgot one important point in my reply. The GC module contains some
useful methods for debugging. Check gc.garbage. It should be empty.

http://docs.python.org/lib/module-gc.html

Christian

[Christian Heimes]

rupert.thurner wrote:

what would be a good means of finding where the 0.11 version of
edgewall trac uses excessive memory. see
http://groups.google.com/group/trac-...16e519da54f16b
for some details, where jonas suggested
http://wingolog.org/archives/2007/11...n-applications
as reading.

tiran already gave some hints on http://bugs.python.org/issue1871, but
also suggested to ask the general mailing list:

Do you have classes with a __del__ method which may create reference
cycles? The GC can't break cycles when a __del__ method is involved.

Are you keeping references to tracebacks, exception objects (except
Exception, err) or frames (sys._getframe())

I forgot one important point in my reply. The GC module contains some
useful methods for debugging. Check gc.garbage. It should be empty.

http://docs.python.org/lib/module-gc.html

Christian

[Jeroen Ruigrok van der Werven]

Hi Christian,

-On [20080119 16:16], Christian Heimes (li***@cheimes.de) wrote:

>I forgot one important point in my reply. The GC module contains some
useful methods for debugging. Check gc.garbage. It should be empty.

Yeah, we're messing around with that stuff as well as many other ways of
trying to track issues, but it can really be looking for a needle in a
haystack to be honest.
There's so much output that, I guess, make sense only when you're semi-deep
into the Python internals to even make heads or tails out of it. =\
And even third-party code is not helping much to reduce the clutter and
provide insight.

--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org/ asmodai
イェルーン ラウフãƒ*ック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
Life is not a problem to be solved but a reality to be experienced...

[Christian Heimes]

rupert.thurner wrote:

i forgot to mention that i cannot see any explicit sys._getframe(), or
__del__ in the genshi code, while the ones in trac-core seemed to be
there in 0.10.4.

Does the code keep a reference to a traceback object or an attribute of
a traceback object?

Christian

[rupert.thurner]

On Jan 20, 2:59*pm, Christian Heimes <[e-mail]:

rupert.thurner wrote:

i forgot to mention that i cannot see any explicit sys._getframe(), or
__del__ in the genshi code, while the ones intrac-core seemed to be
there in 0.10.4.

Does the code keep a reference to a traceback object or an attribute of
a traceback object?

Christian

if there is no other possibility but doing it with sys.exc_traceback,
sys.last_traceback, sys.exc_info, the answer is no for genshi.

[rupert.thurner]

On Jan 20, 2:59*pm, Christian Heimes <[e-mail]:

rupert.thurner wrote:

i forgot to mention that i cannot see any explicit sys._getframe(), or
__del__ in the genshi code, while the ones intrac-core seemed to be
there in 0.10.4.

Does the code keep a reference to a traceback object or an attribute of
a traceback object?

Christian

could you have one look at http://genshi.edgewall.org/browser/t...hi/_speedups.c
?

rupert.