Bug#411577: eog: memory leak viewing jpeg images (with special size?)

[Andreas Juch]

Sven Arvidsson wrote:

> Some images can make eog run amok and eat lots of memory, especially
> certain GIF images. 
> 
> Do you have other images in your home directory? If so, can you try
> moving them one by one, opening with eog and see if this indeed is
> caused by a misbehaving file?
> 
> I noticed that you didn't have the image collection view on, so this is
> a long shot, but it could be worth a try.

Hello!

This was a perfect shot! I had only 5 gif-images of wich one (named
testfile :-)) was 6mb large. I moved them away and the problem was away
too. Gimp managed to open the file (after some time and using a lot of
memory, but less than eog) which turned out to be a screencast i created
in August 2006 with "byzanz-record -c -d 120" testfile running unstable
at that time. The file is a animation with 1280x1024 pixels and about
1400 Frames.

Anyway this is a strange problem because this file was not the one I
opened. Maybe the collection view is generated in the background even
when turned off... Although it's some kind of "problem between chair and
monitor" this is strange.

If you or the eog developers need test-data I'll send the file. Just
mail me (but probably byzanz will generate files causing similar effects).

> I believe valgrind usually is the tool to use when hunting for leaks,
> but it's not something I'm familiar with.

I tried it, but it's a little bit different from the profilers I know.
I'm glad that the cause has been found.

Thanks a lot for your patience!

Andreas