[opensuse-kde] Krunner crash / performance issues

Continuing a discussion that was on the main list, but is more relevant
to this one,

On 01/03/10 16:59, Will Stephenson wrote:
> I guess that it's crashing. KRunner uses multiple 'Runners' running in
> their
> own threads.  If you click the wrench icon at the left side of the
> KRunner
> popup, you can disable individual runners.  Could you try to disable
> individual runners (binary search?) to determine which one is dying?
>
> You can also restart krunner in gdb in a shell to get a backtrace of the
> crashing runner with
> killall krunner && gdb --args krunner --nocrashhandler --nofork
> then 'run', then when it dies 'bt', copy that, finally 'quit' to get
> out of
> gdb, killing the dead and suspended krunner process.
I tried to test some different runners and I learnt a couple of things:
* Some runners don't seem to work at all for me (as in, give no results
even as the only runner loaded, for terms I know should give results).
  + Contacts (maybe because I have migrated my contacts to akonadi?)
  + Control Audio Player (tested against Amarok)
  + Kill (lots of debug output, no actual output)

I don't use sessions so didn't have anything to test the various
*-session runners against. Also, the nepomuk runner didn't give me any
results but I think that's because I have strigi disabled atm.

* The Windows krunner "close", "activate", work, but it crashes reliably
when "shade", "min"/"max", "keep above"/"keep below" is used, taking
down all of krunner

* Under stress, the nepomuk krunner seems to crash according to the
debug output, but restarts without bringing all of krunner down

* The web-lookup runners (wikipedia, wikitravel, techbase) take a while
to return any results (and in the debug output is a message saying
"runner is too slow, putting it on the back burner.") - probably to be
expected.

With the following runners loaded krunner only crashed once in several
days of use, was responsive to typing and quick to open and close:
+ Locations
+ Spell Checker
+ Places
+ Applications
+ Command Line
+ Bookmarks
+ Desktop Sessions
+ Calculator
+ Kopete contact runner
+ PowerDevil
+ Unit Converter
+ Plasma Desktop shell
+ KGet
+ Kate sessions
+ Konqueror sessions
+ Konsole sessions
+ Web browser history
+ Konqueror web shortcuts

The one time I managed to get krunner to crash completely in this
configuration was after about 15mins of constantly opening, typing a few
things, closing, loading a new runner, unloading a runner. This didn't
happen reliably.
Is the attached backtrace any use?

Control Audio player is very bad, and causes krunner to open+close very
slowly / return results very slowly. Could be because I have a ~2000
track Amarok collection it is trying to search, but controlling amarok
(play/pause) doesn't work either. However I don't see an actual crash,
things just seem to stall ...

So the summary of this email is try disabling the "Control Audio
player", "Windows", and web-lookup runners and see if things work
better/faster.

Regards,
Tejas