memory leak

Bug #382267 reported by taka k. on 2009-06-01
44
This bug affects 6 people
Affects Status Importance Assigned to Milestone
CheckGmail
Unknown
Unknown
checkgmail (Debian)
Invalid
Undecided
Unassigned
checkgmail (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: checkgmail

after 11 days of uptime, checkgmail was using more than 50% of total RAM (which amounts to about 256 MB). checkgmail doesn't use this much when started. sorry i can't provide more technical details. please let me know how i can provide more details.

ubuntu 9.04 2.6.28-11-generic x86_64
checkgmail 1.13+svn37-1

hackel (hackel) wrote :

I've currently only been running checkgmail for one day and it's already doubled, using 424m virt, 95m res, and only 6740k shr. When first starting checkgmail, it uses 246m/43m/11m. I imagine using an interpreted language like Perl for a graphical app can't be terribly resource-conscious.

Changed in checkgmail (Ubuntu):
status: New → Confirmed
fuhrysteve (fuhrysteve) wrote :

I have 3gb of ram, and this app frequently uses close to 50% of that. Fantastic program aside from the memory leak.. I just restart it every now and then.

I would love to see this bug fixed, but i doubt there's much the package managers can do about it -- as hackel said, Perl's probably not the greatest choice for a resource-conscious graphical app..

parnote (parnote) wrote :

I can confirm that the memory leak problem with checkgmail is NOT restricted to Ubuntu or debian-based systems. I am currently running another Linux distro, and checkgmail is locking up my 1.6 GHz Centrino processor with 98-100% CPU usage, and consuming extraordinarily large chunks of available user memory (between 75-85% ... I have 1 GB installed on this computer). A SuperKaramba widget that monitors the top memory usage by programs shows that X keeps consuming more and more memory when checkgmail is running. Most of the time, the only way to get back control of my computer is to restart X (Ctrl-Alt-Bkspc). The longer my computer sits idle, the worse the problem is.

Hopefully, this information is useful in finding the memory leak. As it is, I can no longer use checkgmail, despite it otherwise being a very nice program that fills in the void left by no Linux version of Gmail-Notifier in Windows.

kurt belgrave (trinikrono) wrote :

Hey guys
I would love to help you get this bug triaged, firstly can you try the latest (lucid) ubuntu release and then run checkgmail -update and see if this helps.

Changed in checkgmail (Ubuntu):
status: Confirmed → Incomplete
kurt belgrave (trinikrono) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Michael Alexander (ftmichael) wrote :

I ran checkgmail -update a while ago (after my fresh install of Lucid) and it didn't improve the memory leak at all. Just now, after several days of running nonstop, checkgmail was using 453MB of RAM according to the System Monitor. I just restarted checkgmail and now it's using 20MB of RAM, which is what it usually uses when it's freshly started. It continues to use more and more RAM the longer it's running.

kurt belgrave (trinikrono) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

kurt belgrave (trinikrono) wrote :

Launchpad has the ability to watch lots of upstream bug trackers and this can be done by following the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've added the bug watch for this bug report.

Changed in checkgmail (Debian):
importance: Undecided → Unknown
status: New → Unknown
Mark Edgington (edgimar) wrote :

Here's a valgrind log...

Here's another valgrind log from running checkgmail for 24 hours.

Charlie Kravetz (charlie-tca) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: http://sourceforge.net/support/tracker.php?aid=2686715

Changed in checkgmail (Ubuntu):
status: Incomplete → Opinion
importance: Undecided → Low
status: Opinion → Triaged
Changed in checkgmail (Debian):
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.