Memory leak in "Run Application" dialog
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | GNOME Panel |
Fix Released
|
Undecided
|
Unassigned | |
| | gnome-panel (Ubuntu) |
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Binary package hint: gnome-panel
There seems to be a memory leak in the completion feature of the "Run Application" dialog.
Steps to reproduce:
* Start top or the System Monitor to monitor the memory usage of the gnome-panel process in real time.
* Open the "Run Application" dialog
* Type a letter, ("g" for example).
* Wait a few seconds, memory usage goes up a bit (up to 1MB here)
* Press backspace, wait a few seconds, memory usage goes up again.
* Rinse, repeat.
* Close the "Run Application" dialog, the memory is not released.
In a long-running session (several days), if the user regularly uses the "Run Application" dialog, that can cause gnome-panel to bloat up to several hundreds MB.
| David Allouche (ddaa) wrote : | #1 |
| David Allouche (ddaa) wrote : | #2 |
Oh, by the way. I reproduced it in Feisty (gnome-panel 2.18.1-0ubuntu3.1) and today seb128 said he could reproduce it as well.
| David Allouche (ddaa) wrote : | #3 |
"Assistive Technology" seems to play a large part in the problem.
Initially, I had it enabled, and observed 1MB leak (with the letter "g").
Then I disabled it ( opening System-
Then, the same procedure only causes a 0.1MB leak.
| Sebastien Bacher (seb128) wrote : | #4 |
Could be one of the leaks described on http://
| Changed in gnome-panel: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in gnome-panel: | |
| status: | Unknown → New |
I can not reproduce this with Intrepid (gnome-panel 2.24.1-0ubuntu2.2). Seems liike this specific leak has been fixed. Is anyone still getting this?
| David Allouche (ddaa) wrote : | #6 |
I am the original bug reporter. I cannot reproduce the leak on Jaunty (gnome-panel 1:2.26.0-0ubuntu7).
There is no clear relation between this bug and the linked upstream bug. The upstream bug reports a number of leaks detected with valgrind, without explaining what user actions produced it. Examination of the valgrind stack traces in the upstream bug report does not suggest that the run dialog was involved (disclaimer: I am not familiar with this code, I am just using programmer common sense applied to the function names present in the stack traces).
This bug should be unlinked from gnome-bugs #475476 and closed immediately.
| Changed in gnome-panel: | |
| importance: | Unknown → Undecided |
| status: | New → Fix Released |
| Changed in gnome-panel (Ubuntu): | |
| status: | Triaged → Fix Released |
Oh, by the way. I reproduced it in Edgy (gnome-panel 2.18.1-0ubuntu3.1) and today seb128 said he could reproduce it as well.