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 425853 - last-exit uses lots of memory (memory leak?)
last-exit uses lots of memory (memory leak?)
Status: RESOLVED FIXED
Product: last-exit
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Last-exit Maintainer(s)
Last-exit Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-04-03 13:03 UTC by Roel Huybrechts
Modified: 2008-03-30 01:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Roel Huybrechts 2007-04-03 13:03:32 UTC
I use the last-exit player on Ubuntu Feisty (development version). Currently the application uses not less than 138 MB of memory.. That's a little too much for such a small application I guess?

This happens with last-exit version 4-0ubuntu5 included in Ubuntu's Universe repository.
Comment 1 iain 2007-04-07 12:12:20 UTC
How did you get this value of 138meg?
Comment 2 Roel Huybrechts 2007-04-07 16:12:37 UTC
I read it in the process list of gnome-system-monitor.
Comment 3 Brandon Hale 2007-04-08 10:19:47 UTC
Are you looking at Memory (last column) or virtual memory?
Memory = Resident - Shared.
Comment 4 Roel Huybrechts 2007-04-08 15:53:42 UTC
I was looking at the column named 'Resident memory'.
Comment 5 iain 2007-04-08 22:22:17 UTC
You need to subtract the Shared memory from that number to get a less inaccurate indication of memory usage.

I agree that 138meg of memory seems a lot for the Resident memory, but its not an accurate enough measure to access whether there is something wrong.

Here are a link to explain memory usage on linux and why its not such a simple matter as looking at this output

http://wiki.marandcustomsolutions.com/space/Linux/Understanding+memory+usage
Comment 6 Brandon Hale 2008-03-30 01:44:31 UTC
This is almost a year old now, I am going to call it dead.