[snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
I upgraded from Focal to Groovy, and now the first launch of the Chromium snap after a reboot is taking much longer than before. On my main home laptop it takes over 30 seconds, while under Focal I don't remember it taking more than 10 seconds.
I tried another computer I could erase. On Groovy that computer takes nearly a minute to launch the Chromium snap after rebooting. Then I clean installed Focal on the same machine, and the Chromium snap takes just under 10 seconds to launch after a reboot. For both I installed all updates, and I let the computer sit idle for a few minutes after rebooting to try to rule out other activity.
I haven’t noticed the change for any other snap, although I don’t use any that I ever noticed as much of a launch delay as Chromium. (VS Code for one doesn’t seem slower — certainly not taking nearly a minute — but I haven't done a real comparison like for Chromium.)
ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSign
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 20 21:29:20 2020
InstallationDate: Installed on 2020-04-01 (202 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
Snap: chromium 87.0.4280.20 (latest/beta)
SnapSource: ubuntu/
UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)
Changed in chromium-browser (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in chromium-browser (Ubuntu): | |
assignee: | Olivier Tilloy (osomon) → nobody |
Thanks for the report Alexander. This is a concerning regression indeed.
I see in the data attached by apport that you're using the chromium snap from the beta channel.
Were you installing from the beta channel in both cases? Does switching to the stable channel make a difference?
Could you run chromium with the following command in both configurations, and attach the output printed in the terminal after closing the window?
snap run --trace-exec chromium
Thanks!