* Kyrill Detinov
On Mon, 16 Jul 2012 01:03:30 +0200 Guido Berhoerster wrote:
Can you get a valgrind log (install debuginfo packages for all linked libraries and see http://wiki.xfce.org/howto/panel_plugin_debug#debug_with_valgrind_full_examp...) and attach it to the upstream bug you've already opened?
Thanks, Guido.
In my case the plugin is internal. The package provides a library /usr/lib64/xfce4/panel/plugins/libsystemload.so and no executables files.
I don't see examples for debugging internal plugins. Can you help, please?
Oh sorry, I think the internal debugging mode can be used for modules. First, make sure debuginfo packages for all linked libraries and valgrind are installed, then execute "xfce4-panel -q; PANEL_DEBUG=valgrind xfce4-panel" which will quit the current panel instance and start a new one with valgrind running for each plugin. Let it run for a sufficiently long time until memory usage has significantly increased and quit the panel again with "xfce4-panel -q", there will be a log file named /tmp/??????????_valgrind_systemload_??.log, please compress and attach that to the upstream bug. When you do that it might also make sense to subscribe landry@xfce.org to that bug since he last worked on the systemload plugin and might have an idea what's going on. Please also state the exact GTK version (2.4.10?) and the theme/gtk-engine you use. It seems that recent changes have also lead to memory leaks in the cpugraph and netload plugins where the cause it not clear yet (bugs #8521, #8925). -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-xfce+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-xfce+owner@opensuse.org