[Bug 206317] plasma-desktop krunner kded4 memory leak

[Lamarque V. Souza]

https://bugs.kde.org/show_bug.cgi?id=206317





--- Comment #36 from Lamarque V. Souza <lamarque gmail com>  2011-04-15 22:14:54 ---
Valgrind is the tool used to track memory leaks: http://valgrind.org/

I am starting to use it to track problems in my KDE programs. What I do is
start a X session with only xterm opened, open a second xterm in background
(xterm &), then in the first xterm I start kded4 through valgrind:

valgrind -v --leak-check=full --log-file=kded4.log --malloc-fill=0xaa
--free-fill=0xbb kded4 --dograb --nocrashhandler --nofork

Notice the --nofork parameter, the first xterm will be blocked while valgrind
is running, that is why I start a second xterm before valgrind. In the second
xterm I launch the rest of the KDE session by calling startkde.

Be warned that valgrind makes the program starts/run really slow, so be patient
when running a program through valgrind. Be also warned that when kded4 crashes
for whatever reason it is automatically started by kdeinit4 without valgrind
and without the kcrash dialog. So from time to time check if valgrind is still
running.

Good luck.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.