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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900783
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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>
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
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
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
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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
15 matches
Mail list logo
