Freezes on start-up

[deroli-us]

Im using Pop Os 22.04 on Gnome with some of the cosmic Apps.

About half the time i open the Files Manager it just freezes and i cant even close it without ending the process using the system monitor.
This happens on both my Laptop with intel cpu and integrated gpu and my desktop pc with amd cpu and dedicated amd gpu.

max@pop-os:~$ cosmic-files
max@pop-os:~$ [2025-02-23T21:02:32Z WARN  wgpu_hal::gles::adapter] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
[2025-02-23T21:02:45Z WARN  iced_futures::subscription::tracker] Error sending event to subscription: TrySendError { kind: Full }
``

[l-const]

do you have mounted drives?

[givensuman]

do you have mounted drives?

No, just a 1TB SSD.

$  inxi
CPU: 8-core AMD Ryzen 7 7840U w/ Radeon 780M Graphics (-MT MCP-)
speed/min/max: 400/400/5132 MHz Kernel: 6.12.15-200.fc41.x86_64 x86_64
Up: 1h 31m Mem: 7.89/30.65 GiB (25.7%) Storage: 931.51 GiB (2.9% used)
Procs: 483 Shell: fish inxi: 3.3.37

Only caveat about my system might be that I'm on Fedora

Edit: Oops meant to reply to this on #826

[deroli-us]

do you have mounted drives?

yes.
on my Desktop 2 extra disks and 4 nfs shares + nextcloud integration
on my Laptop somewhere between 1-4 nfs shares + nextcloud integration

[johnoye742]

I'll leave my two cents.

I also noticed this and because I use a potato pc, i believed a bigger pc wouldn't have much problems with that- i was wrong.

I believe there are several ways we could go about rhis problem in this project. I'll list them below

• One of them is lazily loading the files one-by one and updating the UI as it comes, I believe this is better than just loading everything at once with no feedback at all.
• A better way would be chunking. Imagine we could fetch the files in chunks and have like Vec that held all those chunks and while pushing chunks to the Vec it could be updating the UI accordingly. It could be in chunks of 30, 50 or even 100. That would be better UX and even for systems fast enough it wouldn't even be noticeable.
• Another less effective but simpler method would be to show a loading screen just to give the user some feedback that files are being loaded, perhaps they should wait. That's better UX than no feedback at all.

I am willing to do the fixes with any of this methods or any other suggested if I'm sure I have the support of the leaders of the project.

I'd also like to mention @jackpot51 to take a look at this.

Thanks.

[lnicola]

It's not so bad for me, but there's about a 200 ms delay when opening. The delay is between showing the bookmarks, Networks label and an empty right pane, and my drives, online account (from GNOME) and files in my home directory showing up.

I don't know if it's the drive or file enumeration that's slow.

[phlepper]

I don't know that I have the same problem, but I have a consistent 13 second "freeze" when starting the COSMIC Files app (using Pop 24.04). It takes 13 seconds to display the folder contents (the main window displays immediately). If I click on something other than Home (during the 13 second interval), it still takes the total 13 seconds to display the new folder. If I click on the close "x" during the 13 seconds, it still takes the full 13 seconds and then the window / app closes. Once the first 13 second "hang" is over, everything works fine and switching folders / disks / network drives is fine.

I see this error in journalctl every time I start the app:

pop-os systemd[2691]: Failed to start app-cosmic-com.system76.CosmicAppList-125137.scope - Application launched by COSMIC.

Let me know if I should open a separate ticket for this or if you'd like more information (as I can easily reproduce this every time I open the Files app).

Paul

[WatchMkr]

This may have been fixed with #958. Is anyone still experiencing this issue?

[givensuman]

This may have been fixed with #958. Is anyone still experiencing this issue?

No, I stopped noticing any issues, although I reinstalled my OS several times over the past couple of months so wouldn't be able to pinpoint when it stopped happening.