How to find memory leakage in x image code?

How to find memory leakage in x image code?

[joakim]

I'm using my Imagemagick patch I posted a while ago a lot to work with
scanned documents.  They are mostly 300dpi A4 BW djvu images.

After viewing something like 100 images or so, the entire X session
frequently crashes.

I cant figure out where the leakage is. Killing the image buffers doesnt
help. The image cache is supposed to be flushed frequently enough for X
not to crash right?

The basic allocation/deallocation is the same as for most other
image type supports in emacs. Does someone else experience the same
problem with viewing a large number of SVG images for instance?

-- 
Joakim Verona

Re: How to find memory leakage in x image code?

[Stefan Monnier]

> The basic allocation/deallocation is the same as for most other
> image type supports in emacs. Does someone else experience the same
> problem with viewing a large number of SVG images for instance?

Don't know about SVG, but at least I often view many PNG images (via
docview-mode displaying a PDF document) and haven't noticed any
related problem.  This is no guarantee, of course.


        Stefan

Re: How to find memory leakage in x image code?

[Markus Triska]

joakim@verona.se writes:

> The basic allocation/deallocation is the same as for most other
> image type supports in emacs. Does someone else experience the same
> problem with viewing a large number of SVG images for instance?

There once was a leak (that's now fixed) in SVG viewing, please see:

   http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=576

for a test case that I hope you find useful for your case as well.