© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
Binary package hint: gedit
It seems gedit doesn't release the memory used to open a file when closing it making it so use ridiculous space in ram for little files if you opened a big file and closed it. Strangely gnome system monitor reports a lower memory use under the processes tab, but reports the used ram in the resources tab and top actually gives the high amounts of used ram.
To try this:
1- open gedit
2- open top
3- notice the ram use: 19393 weltall 20 0 38980 19m 10m S 0 0.7 0:00.79 gedit
2- get a big file to open (mysql dumps are the best to try. I've tried with a ~50 mb dump)
3- you will notice an higher ram use, for sure > 300mb to open a 50mb file is a bit excessive but this is still an optimization issue which goes beyond this bug report: 19393 weltall 20 0 342m 305m 12m S 2 10.1 3:02.14 gedit
4- close the tab which had the file
5- check again top no changes in ram use: 19393 weltall 20 0 342m 305m 12m S 0 10.1 3:02.85 gedit
this is definitely a memory leak or a bad ram retaining for future use implementation
6- try to reopen the file, gedit will take the same time to parse the file, but the increase of ram use is more little: 19393 weltall 20 0 381m 345m 12m S 0 11.4 6:01.23 gedit
7- close the file again the ram use doesn't change again
other gnome applications have similar leak issues like nautilus which after some days takes more than 300mb like nothing and closing windows doesn't release ram so maybe the problem might reside in underlying libraries.
i'm using ubuntu intrepid with all the updates from normal repositories (altough this bug has been present since various releases)
Description: Ubuntu 8.10
Release: 8.10
gedit:
Installed: 2.24.2-0ubuntu1
Candidate: 2.24.2-0ubuntu1
Version table:
*** 2.24.2-0ubuntu1 0
500 http://
100 /var/lib/
2.
500 http://