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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900783
Title:
[snap] On Groovy, Chromium snap takes much longer to load the first
time after reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
