Bug 478042

Summary:	very slow loading time on first launch
Product:	[Plasma] krunner	Reporter:	Henning <boredsquirrel>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	alexander.lohnau, bugseforuns, natalie_clarius
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	a single first launch of krunner A first launch and a second launch of krunner

Description Henning 2023-12-04 12:13:42 UTC

Unlike the global menu, when using KRunner as the search for Applications etc, it is not a good experience.

The problem is that it doesnt load in the background, so the first launch is very slow and loses quite a lot of keypresses

Please load krunner in the background somehow, to circumvent this.

Specified App:
kf5-krunner-5.111.0-1.fc39.x86_64

--- Software ---
OS: Fedora Linux 39.20231202.0 (Kinoite)
KDE Plasma: 5.27.9
KDE Frameworks: 5.111.0
Qt: 5.15.11
Kernel: 6.6.2-201.fc39.x86_64
Compositor: wayland

--- Hardware ---
CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 21.4 GB
GPU: AMD Radeon Vega 8 Graphics
Video memory: 2048MB
Audio: Pipewire

Comment 1 Alexander Lohnau 2023-12-04 18:42:13 UTC

Can you try running a profiler on KRunner or disable some plugins?

After disabling a plugin, run "kquitapp5 krunner" to ensure you have a fresh start.

Comment 2 Henning 2023-12-05 01:35:37 UTC

Hm, not sure if this is that important.

Krunner loads normally fast but only after it loaded once. I disabled some 3rd party plugins and the result is exactly the same.

I will use perf to maybe get some more info, but it really seems like some background loading would be best

Comment 3 Henning 2023-12-05 01:57:20 UTC

Created attachment 163882 [details]
a single first launch of krunner

recorded with hotspot and perf

Comment 4 Henning 2023-12-05 01:58:13 UTC

Created attachment 163883 [details]
A first launch and a second launch of krunner

maybe the second launch is not recorded, as the first launch came through perf, the second one through the keyboard shortcut.

Comment 5 Alexander Lohnau 2023-12-05 19:26:23 UTC

I don't see anything suspicious there. Is there any output on the command line? Maybe the problem is on the UI side of things and not related to the framework.

Comment 6 Henning 2023-12-05 22:33:23 UTC

CLI gives no output.

I just created a desktop entry and set it to autostart. Now I dont have this anymore, because I am certain it can just be fixed by autostarting krunner, preloading the needed resources etc.