I copied the "common" directory of ~/snap/chromium to a local filesystem
(1Gb ) and created a symlink to point to the local version.
When I start chromium I then get:
mkdir: cannot create directory '/home/wolff/snap/chromium/common': File
exists
and chrome refuses to start. I then restored my
(earlier this week:) To debug this further I started chromium under
"strace -f -o /tmp/..." : Must be run as root. Hmm.
Today I tried something different. I used strace on ALL 33 chrome
processes. Many did something every second or so, just one was in a
tight loop. This is also the process that
I just measured the network trafic that chromium is causing It is
about 23000 network packets per second.
--
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/1893650
Title:
OK. Done. Downloaded, tested: Nope, google-chrome-stable does not show
this behaviour.
--
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/1893650
Title:
Chromium snap causes
(posting this from Chromium again, and immediately I see the network
traffic ballooning. It does look a bit as if the linux "select"
behaviour: modify the timeout to show time remaining is involved: It
takes like 15 seconds of medium traffic before stuff is back to the
original level again. My
Thanks for the report rew.
For testing purposes, could you download the google chrome installer from
google.com/chrome, install it and test whether it is behaving similarly? That
would be a useful data point. Thanks!
--
You received this bug notification because you are a member of Desktop
6 matches
Mail list logo
