Why are cosmic apps so slow to load?

My laptop is running modern hardware with NVME drive and has 64GB of RAM. Running Pop!_OS 22.04 with Gnome/Wayland.

When I launch the cosmic-store or cosmic-edit (for example) via command line or launcher, each takes about 25 seconds for its app window to load. Loading the Pop Shop in the same fashion takes less than 1 second.

I saw a few lines indicating files couldn’t be opened, and thought at first maybe my ulimit was set incorrectly, but there is plenty of headroom on my user (soft limit: 4096, hard limit: 1048576).

I do see a handful of logs that look questionable:

May 04 07:50:59 rosie systemd[2109]: app-gnome-com.system76.CosmicEdit-17126.scope: Couldn't move process 17126 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-com.system76.CosmicEdit-17126.scope': No such process
May 04 07:50:59 rosie systemd[2109]: app-gnome-com.system76.CosmicEdit-17126.scope: Failed to add PIDs to scope's control group: No such process
May 04 07:50:59 rosie systemd[2109]: app-gnome-com.system76.CosmicEdit-17126.scope: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
May 04 07:50:59 rosie systemd[2109]: Failed to start Application launched by gnome-shell.

What could be causing the cosmic apps to load so slowly?

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like “RTM” or links to LMGTFY. Linking to direct sources that answer the asker’s question is fine, but it’s advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic “It’s bad” or other simple negative comments don’t help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don’t post malicious “advice”

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn’t serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

canadaduaneOP English

0·

6 months ago

Thanks. Strangely, after using WGPU_POWER_PREF=high, it is always fast for me, even when I don’t specify this preference. I don’t understand it. In any case, I guess it’s “fixed” for now, so thanks!

canadaduaneOP
fedilink
English
arrow-up
1·
edit-2
6 months ago
I no longer think WGPU_POWER_PREF has any bearing on the fast/slow issue, see my other comment.