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

[Sven Arvidsson]

On Fri, 2007-03-02 at 01:44 +0100, Andreas Juch wrote:
> I just wanted to write, that the problem diappeared. But then I found
> out that eog only shows this behaviour when started by doubleclicking
> the image file from an open nautilus showing my home directory. The same
> file copied to ~/Desktop or /tmp and doubleclicked from there, doesn't
> make eog act that bad. Image sizes are not relevant. I just tried with
> smaller images, the same.

Hi again,

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.

> So the combination of nautilus pointed to my ~ and eog seems to cause
> that problem. I tried the "debug recipe" from Bug #411801, but I just
> don't have any gdb debugging and very little C-programming experience,
> so this didn't enlighten me...

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

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20070305/e7b240ec/attachment.pgp