https://bugs.kde.org/show_bug.cgi?id=491203
Bug ID: 491203
Summary: Cold start is slower than subsequent calls
Classification: Plasma
Product: krunner
Version: 6.1.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: gudvinr+...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
Target Milestone: ---
SUMMARY
First time you launch krunner, it happens with noticeable delay.
Subsequent launches do not have it.
One could say that "since it's only first time it doesn't matter". However,
since it is a tool for quick actions, it becomes very annoying because this is
ruining workflow that you experience basically all other time you use krunner.
krunner probably need to do some startup work but clearly it is only done once.
If this work can be done asynchronously, it should be done asynchronously.
krunner window should be shown as soon as possible even if this work isn't done
at the moment you see it.
It is very likely that background work will be already done when you finish
typing query because while lag is there, it is not that long.
Even if it isn't easy to do this asynchronously with typing query in parallel,
another option is to show krunner window and disable input and unlock when work
done. In this case at least krunner feels responsive.
In case if lag caused by caching qml stuff or whatever it needs for rendering,
plasma can do that stuff before first krunner launch.
STEPS TO REPRODUCE
1. Reboot
2. Press krunner shortcut
OBSERVED RESULT
krunner starts with delay
EXPECTED RESULT
No delay
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.2-arch1-1 (64-bit)
Graphics Platform: X11
--
You are receiving this mail because:
You are watching all bug changes.
