onagre takes a long time to open

[TurtleMeds]

Describe the bug
onagre takes about 6-10 seconds to open.

Config
default

To Reproduce
launch time onagre
spam escape
look at time

Expected behavior
open in a reasonable time

Screenshots

Window manager (please complete the following information):

• Hyprland

Additional context
Arch linux
AMD Ryzen 5 7530U
16 gb of memory

[oknozor]

I have seen this before without being able to find a reproducer.
Does this still happen on consecutive launches ?

[salahoued]

I have compiled the 1.1.0 on openSUSE Tumblweed, and I found it lagging even when typing and displaying results.

[oknozor]

Do you have the same behavior woith icons disabled ?

[salahoued]

Sorry, but how can I do that?

[oknozor]

you can copy paste this config https://docs.onagre.dev/gallery.html#murz

[salahoued]

Way better now, especially the search is fast,
The start up didn't take as much time.

EDIT: tried the default theme, and Hollow theme, they have the same issue, especially the default theme it takes even more time to start up

Thanks

[oknozor]

Thanks for the report, we probably need to cache icon paths. I'll do this asap.

[salahoued]

Hi @oknozor , I'm not sure about @TurtleMeds , but for my part, it is most likely because of the icon-theme used in the
configuration, for example the Hollow theme uses the Papirus icon theme which I don't have installed, when modifying the hollow.scss theme to use the Breeze icon theme the startup is much faster.

I don't know which icon theme the default theme uses, but it still has the same issue.
Where can I find the .scss file for the default theme?

[oknozor]

The default theme is hardcoded, it uses Adwaita I think

[issmirnov]

I am experiencing the same. Arch Linux, Intel 12900k with SSD. Time shows 0.778 to open and close with escape. theme is Murz.

I am comfortable compiling and running dev builds to help reproduce or narrow down a fix.

[belkka]

Same in Xorg, XFCE (not specific to Hyprland). It looks like startup time is very sensitive to system load. I was doing these tests while doing Arch Linux system update in a background terminal window (downloading large files, compiling etc), got 12 and 14 sec on some runs, but even 500ms feels too much.

I just switched from ulauncher, which has ulauncher command to start background process (should be put in autostart) and separate ulauncher-toggle to actually invoke the launcher, quickly (should be put in keybindings): Ulauncher/Ulauncher#777.