After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760020 - Memory not freed by GIMP even after the particular image (view) is closed
Memory not freed by GIMP even after the particular image (view) is closed
Status: RESOLVED DUPLICATE of bug 725177
Product: GIMP
Classification: Other
Component: General
2.8.10
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-12-31 07:32 UTC by Mohan
Modified: 2016-01-04 18:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mohan 2015-12-31 07:32:37 UTC 
GIMP does not free the memory it occupies even when a particular image that is being worked on is closed. Issue persists even after clearing Document History.

This is what happened: I was working on a 2500x3500 image, and GIMP occupied close to 1.4GB of RAM (I has set the tile cache size to 1.5GB). I closed the image, but GIMP continued to use the same amount of RAM. I tried clearing the undo history before closing, and the document history after closing, but the issue remained. I opened another image of the same resolution, which led to GIMP starting to use the swap space, at which point everything just stalled - probably because I'm working on an old system (2GB ram, Intel core 2 duo).

The only way around it was to close GIMP after I was done with a file, and restart GIMP to work on a new file. This ought not to be the case, right?

I'm using Kubuntu 14.04, with Awesome Window Manager. GIMP version 2.8.10.

This bug is possibly related to https://bugzilla.gnome.org/show_bug.cgi?id=725177
Comment 1 Michael Natterer 2016-01-04 18:02:19 UTC 
Yes this is most definitely the same issue.

*** This bug has been marked as a duplicate of bug 725177 ***