[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
This seems not to be an issue any more. Feel free to reset the status if otherwise. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Fix Released 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
That's very good news, although there is no fonts-specific change/fix in that revision. That revision uses LZO compression, which trades snap size (from ~172MB to 252MB) for startup speed. I'm glad this improves the situation so significantly! I am also working on a specific fix for font cache generation (using the gnome-3-28 snapcraft extension to build the snap), so I'll keep this bug open to track progress on this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
On my test computer at least, today's snap revision 1373 seems to have solved it. Running `snap run --trace-exec chromium` on a cold boot I get Slowest 10 exec calls during snap run: 0.237s snap-update-ns 0.400s /usr/lib/snapd/snap-confine 0.087s /snap/chromium/1373/snap/command-chain/snapcraft-runner 0.590s /snap/chromium/1373/bin/desktop-launch 0.065s /usr/bin/snapctl 0.114s /snap/chromium/1373/bin/chromium.launcher 0.159s /usr/bin/dbus-send 0.286s /usr/bin/xdg-settings 3.609s /proc/self/exe 5.238s /snap/chromium/1373/usr/lib/chromium-browser/chrome Total time: 6.515s -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
If I started once already, deleting the fontconfig cache ("rm
~/snap/chromium/common/.cache/fontconfig") brings back some slow results
for me on Fedora 33
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900783
Title:
[snap] On Groovy, Chromium snap takes much longer to load the first
time after reboot
Status in chromium-browser package in Ubuntu:
Confirmed
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
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
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/+source/chromium-browser
UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
Marking confirmed because this was also reported as bug #1901432. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
FWIW I hadn't tried Google Chrome on this computer, so I installed it (same stable version as the snap), and it loads with normal speed on cold boot and subsequently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
** Attachment added: "chromium.trace" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+attachment/5426143/+files/chromium.trace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
Thanks Alexander, that's useful data. What this shows is that it's the chromium executable that is taking a very long time to start up on cold boot, there doesn't seem to be any significant overhead from snapd and wrapper scripts. Next thing to try is: snap run --strace="-vvr" chromium 2> chromium.trace and attach the resulting chromium.trace file. This should give us more information about what is taking so long when running the chromium executable for the first time after a cold boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
Here's after a reboot, again with a clean profile that's been opened one time, stable channel on up-to-date Groovy: ab@mb:~$ etrace exec /snap/bin/chromium 2020/10/23 10:27:06 xdotool.go:84: Gtk-Message: 10:27:14.094: Failed to load module "canberra-gtk-module" Gtk-Message: 10:27:14.116: Failed to load module "canberra-gtk-module" [11797:11797:1023/102734.021699:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. 61 exec calls during snap run: Start Stop ElapsedExec 0 472100472.100019ms /snap/bin/chromium 27013 37971 10.958909ms/usr/lib/snapd/snap-seccomp 1033121054872.174139ms /usr/lib/snapd/snap-device-helper 1058381079592.121925ms /usr/lib/snapd/snap-device-helper 1083191105012.181053ms /usr/lib/snapd/snap-device-helper 1108501130802.230882ms /usr/lib/snapd/snap-device-helper 1134211154892.067089ms /usr/lib/snapd/snap-device-helper 1157721180212.249002ms /usr/lib/snapd/snap-device-helper 1183351205682.233028ms /usr/lib/snapd/snap-device-helper 1208671258474.980087ms /usr/lib/snapd/snap-device-helper 1261981285402.342939ms /usr/lib/snapd/snap-device-helper 1288601315772.716064ms /usr/lib/snapd/snap-device-helper 1319401346342.694845ms /usr/lib/snapd/snap-device-helper 1349731374542.481937ms /usr/lib/snapd/snap-device-helper 1378061405052.698183ms /usr/lib/snapd/snap-device-helper 1409621437702.808809ms /usr/lib/snapd/snap-device-helper 1441081463012.193927ms /usr/lib/snapd/snap-device-helper 1465911487782.187013ms /usr/lib/snapd/snap-device-helper 1492171514942.276897ms /usr/lib/snapd/snap-device-helper 1518471543672.520799ms /usr/lib/snapd/snap-device-helper 1554221578772.454996ms /usr/lib/snapd/snap-device-helper 1651571675552.398014ms /usr/lib/snapd/snap-device-helper 1689471713602.413034ms /usr/lib/snapd/snap-device-helper 1728261750122.186059ms /usr/lib/snapd/snap-device-helper 1760981784162.318859ms /usr/lib/snapd/snap-device-helper 1794351820032.568006ms /usr/lib/snapd/snap-device-helper 1830771856622.584934ms /usr/lib/snapd/snap-device-helper 209460445437235.977888ms snap-update-ns 45856646876610.200023mssnap-update-ns 472100573029100.929975ms /usr/lib/snapd/snap-exec 5730295822699.239912ms /snap/chromium/1362/command-chromium.wrapper 5822691204112 621.842145ms /snap/chromium/1362/bin/desktop-launch 66731067941412.10308ms /bin/date 7716567809519.294986ms /usr/bin/md5sum 7844707930448.574008ms /bin/cat 7957228035557.83205ms /usr/bin/md5sum 8058818116555.774974ms /bin/cat 81351383244718.934011ms/bin/grep 83952286876729.245853ms/bin/mkdir 89845195380455.353879ms/usr/bin/head 95683597338116.54601ms /usr/bin/head 97643499345717.022132ms/usr/bin/head 9960591011866 15.806198ms/usr/bin/head 1014738 1030759 16.021013ms/usr/bin/head 1033776 1050442 16.666889ms/usr/bin/head 1053074 1068875 15.800952ms/usr/bin/head 1071585 1088642 17.056226ms/usr/bin/head 1091500 1107697 16.196966ms/usr/bin/head 1115821 1135473 19.652843ms/bin/mkdir 1141314 1162826 21.512031ms/bin/ln 1166500 1186408 19.907951ms/bin/rm 1187048 1201411 14.36305ms /bin/ln 1204112 1326992 122.879981ms /snap/chromium/1362/bin/chromium.launcher 1213257 1251816 38.558959ms/usr/bin/cut 1214077 1236867 22.789955ms/usr/bin/id 1236932 1251408 14.475107ms/usr/bin/getent 1255490 1326690 71.200847ms/usr/bin/snapctl 1326992 54340631 53.013638973s /snap/chromium/1362/usr/lib/chromium-browser/chrome 10571131 54331553 43.760421991s /proc/self/exe 29713400 30021182 307.781934ms /usr/bin/xdg-settings 29913347 30020597 107.249975ms /usr/bin/dbus-send Total time: 54.387691975s Total startup time: 54.414637346s Here's a few minutes later as a comparison of a re-launch: ab@mb:~$ etrace exec /snap/bin/chromium 2020/10/23 10:33:04 xdotool.go:84: Gtk-Message: 10:33:05.870: Failed to load module "canberra-gtk-module" Gtk-Message: 10:33:05.878: Failed to load module "canberra-gtk-module" [13532:13532:1023/103306.073051:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. 55 exec calls during snap run: StartStop
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
Thanks for the data Alexander. To debug this further, could you install etrace, run the chromium snap through it after a cold boot, and share the output? sudo snap install etrace --candidate --classic etrace exec /snap/bin/chromium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
And for my main computer, Groovy/Chromium beta channel *with* my normal profile: alexander@elcste:~$ snap run --trace-exec chromium [sudo] password for alexander: Gtk-Message: 21:19:28.762: Failed to load module "canberra-gtk-module" Gtk-Message: 21:19:28.790: Failed to load module "canberra-gtk-module" [3494:3494:1022/211947.584671:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. Slowest 10 exec calls during snap run: 0.198s snap-update-ns 0.330s /usr/lib/snapd/snap-confine 0.058s /usr/bin/head 0.495s /snap/chromium/1366/bin/desktop-launch 0.045s /usr/bin/snapctl 0.098s /snap/chromium/1366/bin/chromium.launcher 0.134s /usr/bin/dbus-send 0.196s /usr/bin/xdg-settings 35.202s /proc/self/exe 43.764s /snap/chromium/1366/usr/lib/chromium-browser/chrome Total time: 44.773s I could try stable channel and a fresh profile using another user account if it's helpful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
On my main/home computer I've only tried beta channel, but with the other computer I've tried both stable and beta. It doesn't seem to make a difference. Here is what I got for that command on Groovy: STABLE ab@mb:~$ snap run --trace-exec chromium [sudo] password for ab: Gtk-Message: 17:25:22.173: Failed to load module "canberra-gtk-module" Gtk-Message: 17:25:22.194: Failed to load module "canberra-gtk-module" [4206:4206:1022/172540.610350:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. Slowest 10 exec calls during snap run: 0.254s snap-update-ns 0.436s /usr/lib/snapd/snap-confine 0.618s /snap/chromium/1362/bin/desktop-launch 0.115s /snap/chromium/1362/bin/chromium.launcher 0.118s /usr/bin/dbus-send 0.227s /usr/bin/xdg-settings 0.121s /snap/chromium/1362/usr/lib/chromium-browser/chrome 0.094s /usr/bin/xdg-settings 36.826s /proc/self/exe 46.485s /snap/chromium/1362/usr/lib/chromium-browser/chrome Total time: 47.862s BETA ab@mb:~$ snap run --trace-exec chromium [sudo] password for ab: Gtk-Message: 17:31:19.827: Failed to load module "canberra-gtk-module" Gtk-Message: 17:31:19.851: Failed to load module "canberra-gtk-module" [4553:4553:1022/173142.433976:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. Slowest 10 exec calls during snap run: 0.228s snap-update-ns 0.389s /usr/lib/snapd/snap-confine 0.095s /snap/chromium/1357/snap/command-chain/snapcraft-runner 0.607s /snap/chromium/1357/bin/desktop-launch 0.072s /usr/bin/snapctl 0.123s /snap/chromium/1357/bin/chromium.launcher 0.115s /usr/bin/dbus-send 0.315s /usr/bin/xdg-settings 31.778s /proc/self/exe 44.545s /snap/chromium/1357/usr/lib/chromium-browser/chrome Total time: 45.843s I deleted the chromium data (rm -r ~/snap/chromium), launched chromium once, then rebooted and waited briefly, and finally ran the command. Then I refreshed channels and did the same again. If it's useful I can reinstall Focal on that computer when I'm back at work tomorrow, and get the same info. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
Testing in fully up-to-date focal and groovy virtual machines, I do see a slightly longer startup time in groovy after a cold boot, but it's not a 3× increase. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
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! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Incomplete 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 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip 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/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
