[Bug 357036] Re: memory leak discovered in system monitor

2009-06-11 Thread Sebastien Bacher
closing since that works correctly now ** Changed in: gnome-system-monitor (Ubuntu) Status: Incomplete = Invalid -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 357036] Re: memory leak discovered in system monitor

2009-05-01 Thread warren
Bug retracted; most likely symptom of bug #307472, does not seem to appear unless launched with toolbar plugin, or may have been fixed during upgrade/patch. -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-11 Thread Sebastien Bacher
you say that the software has incorrect memory usage, how much difference in use did it get during the time where you got the valgrind log? because the valgrind log has no obvious extra use showed -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-11 Thread warren
The memory use was about 2 gigs off. -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-10 Thread warren
What difference? Could you clarify your question? I thought I explained in my observances in my last comment. The system was behaving as I would expect when ram was full and swap was heavily taxed, and top agreed with me. I took a peek at the log and it appears that no libraries have been tooled

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-08 Thread warren
I have launched the gnome system monitor under valgrind as per instructions, however it is slow, I think it may take all day to reproduce the problem. -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-08 Thread Sebastien Bacher
the system monitor is using that library so you would see the issue in the software the same way, how do you that's not it? -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-08 Thread warren
Here is the valgrind log. The system monitor became unresponsive and fail to update screen a minute or two in, so I was not able to get any information from it, but memory was being consumed. Just recently my other applications became highly unresponsive, so I shut them down, waiting until the

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-08 Thread Sebastien Bacher
right the applet is a toolbar thing, they use the same library to get informations though -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. --

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-08 Thread Sebastien Bacher
the log has no obvious memory usage error, what difference did you have when you closed it? -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. --

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-07 Thread warren
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24944164/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24944165/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/24944166/ProcStatus.txt -- memory leak

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-07 Thread Sebastien Bacher
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. ** Changed in:

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-07 Thread Sebastien Bacher
the issue could be bug #307472 -- memory leak discovered in system monitor https://bugs.launchpad.net/bugs/357036 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-07 Thread Pedro Villavicencio
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. ** Changed in:

[Bug 357036] Re: memory leak discovered in system monitor

2009-04-07 Thread warren
with respect to bug #307472 That sounds familiar, but I definitely think it is the system monitor, because I reproduced the problem three times in one night, and the second time I returned memory use back to normal by closing the system monitor rather than the panel plugin. Also, the third