20 Mar
2013
20 Mar
'13
11:10 a.m.
2013/3/12 Timothy Pearson <kb9vqf(a)pearsoncomputing.net>
I've noticed a quite different but may be similar problem:
Then kicker starts in parallel to kdesktop (e.g. on session start) it loads
the cpu to 100% for several seconds (on core i5)
Kicker transparency is on.
Wallpaper is huge (5 302x3 802) hubble photo.
Seems there are some problems with caching resized images, because
according to valgrind it spends most of time in jpeg-related functions.
Also I've got some lags when I'm switching to that desktop.
On 12 March
2013 10:54, Calvin Morrison <mutantturkey(a)gmail.com> wrote:
http://bugs.pearsoncomputing.net/buglist.cgi?quicksearch=kicker
I would also try setting up a fresh profile and see if it's still
occuring.
More helpful would be to attach GDB to the runaway process and post a
backtrace. gdb --pid $PID_OF_KICKER will attach gdb, then 'bt' will print
the backtrace.
Tim