You are not logged in.
Hi,
After the latest Chromium update started to notice that every time I start it, the window will become non-responsive for 5-10 minutes, after which it goes back to normal. Looking at htop, from the many chromium processes starting, there are always 2 that eats up 100% of CPU (each, that's 2 out of 4 CPUS since it's a multicore system).
One of the 100%-er is the base chromium process
/usr/lib/chromium/chromium --enable-webgl --ignore-gpu-blacklist
which is probably fine. The other one of the two is always something like this (though the exact numbers in the parameters change.
/usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtrials=ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOn/Prerender/PrerenderEnabled/PrerenderLocalPredictor/Enabled/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_06/UMA-Uniformity-Trial-1-Percent/group_95/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_02/UMA-Uniformity-Trial-50-Percent/group_01/ --extension-process --channel=20155.12.1922684424
There are a bunch of other chromium processes with --force-fieldtrials, but there's always one, and always there's one that hangs everything at start.
Did anyone else experience this? Any recommendation why it might happen and how to mitigate it?
My version is 29.0.1547.62-1, will file a bug report if it's not just me.
Offline