Comment 8 for bug 1900783

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.