GNOME Bugzilla – Bug 166275
gThumb doesn't freeze memory
Last modified: 2006-09-13 13:45:45 UTC
Take a large directory with a lot of images (more than 1000 of 800x600 more or less). View them one after the other repetitiveness. Make some operations with some of them, like renaming and removing some. Slowly the memory use of gThumb 2.4.0 goes up and up and up... until a moment when the whole linux (2.6.8 from Ubuntu) doesn't work almost because providing messages that can not allocate new memory for new processes. (In this moment, with Gnome is quite hard to kill gThumb since the computer is almost not responding: so so slowly only).
I confirm this, with browsing a 1000 pic folders. No picture modifications. Changing dirs doesn't release memory. Perhaps, like mozilla, gthump is «caching» everything (maybe just thumbnails) without releasing anything.
Also when importing photos - I have 1GB card in the camera and 256MB of RAM. gThumb is unable to import all photos because it does not fit into memory (and swap) - it just crashes. Or is OOM-killed.
*** Bug 310434 has been marked as a duplicate of this bug. ***
*** Bug 310749 has been marked as a duplicate of this bug. ***
Confirming because of the duplicates.
*** Bug 312236 has been marked as a duplicate of this bug. ***
I have found two memoryleaks, one of them quiet serious: A g_list of all images in the current directory is leaked every time a new image is shown. The following patch reduces the problem significantly.
Created attachment 59150 [details] [review] patch of memoryleaks
patch applied (with some modification), thanks.