https://bugzilla.novell.com/show_bug.cgi?id=338737
User vuntz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=338737#c3
--- Comment #3 from Vincent Untz
AFAIK, the breakpad noise is a function of exception handler initialization code
Ah maybe. Apologies.
, i.e. "I'm ready to handle exceptions" code, distinct from "I'm actually handling an exception" code. If gnome-panel crashed, it crashed because I hit Ctrl-C, which is how I terminated the valgrind session. I sincerely believe that if a program can't clean up its memory properly in response to SIGINT, it's a bug
I'm nearly sure that 99% of the programs out there don't properly clean up the memory on SIGINT. The reason is that the memory will be returned back anyway since the process is exiting and the exit path is not the normal one.
but if you have alternative advice on how to detect memory leakage in gnome-panel, I'm interested in hearing it.
Just run "gnome-session-remove gnome-panel" to have the panel properly exit :-)
In any case, I'm unable to generate a valgrind log that's devoid of breakpad spewage. If that renders this bug report INVALID, then I guess there's not much I can do.
Updated valgrind log with G_SLICE=always-malloc (and the same old breakpad spewage) attached.
Thanks. There's at least one leak in the multiload applet. I'll send a patch for this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.