https://bugzilla.novell.com/show_bug.cgi?id=777527
https://bugzilla.novell.com/show_bug.cgi?id=777527#c24
--- Comment #24 from Guido Berhörster 2013-03-21 08:22:58 UTC ---
You cannot directly compare smem output like that, what you can do is to look
for unusually high memory consumption of a process that keeps growing, ie.
indicators for a memory leak, and then investigate that particular process
further with valgrind.
In order to do that you first need to install all required debug symbols. The
easiest way is by running the application once in gdb which will give you a
neat list of zypper commands. Run the following for xfce4-terminal which stands
out in your list above:
gdb -ex 'set logging on' -ex 'run' -ex 'quit' /usr/bin/xfce4-terminal
Then quit xfce4-terminal and you should have the a gdb log file gdb.txt. Next,
run the following in order to install all required debuginfo packages (make
sure the openSUSE Debug repos are enabled):
awk '/^Try: zypper/ { $1 = "sudo"; print }' gdb.txt | sh
After that you can run the application in valgrind as follows:
G_SLICE=always-malloc G_DEBUG=gc-friendly,resident-modules valgrind
--tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20
--log-file=valgrind-xfce4-terminal.log /usr/bin/xfce4-terminal
Now use the application for a long enough time until memory usage has grown
significantly, then quit it and you have a log file valgrind-xfce4-terminal.log
which shows potential leaks.
You can use the same procedure for other applications such as xchat,
xfce4-panel or some other GTK2 application showing this problem, though firefox
is probably not worth it. Attach the valgrind logs here, maybe we can get some
hint from them.
--
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.