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: Chromium snap causes network traffic. (Duh!) Status in chromium-browser package in Ubuntu: New Bug description: When Chromium is running (but otherwise idle!), there is NFS traffic between my workstation and the NFS server here. On the order of 24000 packets per second. Several tens of packets, OK. several hundreds: mwah. But this is outrageous. When strace-ing the chrome process I see: poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=31, events=POLLIN}, {fd=32, events=POLLIN}, {fd=137, events=POLLIN}], 5, 0) = 0 (Timeout) recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) It uses poll to wait for events... and then gets informed: A timeout occurred, no filedescriptors are ready and then STILL Tries to read from fd 31 and 32. Furthermore, the process seems to specify a 0 timeout as quite often I see the poll call return in about 20-50 microseconds. The process that is doing this shows as: /snap/chromium/1284/usr/lib/chromium-browser/chrome --no-default- browser-check --no-first-run --password-store 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) chromium-browser: Installed: 84.0.4147.105-0ubuntu0.20.04.1 Candidate: 84.0.4147.105-0ubuntu0.20.04.1 Version table: *** 84.0.4147.105-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 3) I expect chromium to use little to no resources (CPU, network) when I'm not actively using it. (asking for small memory footprint is not currently realistic). 4)_ Chromium seems to do something that requires NFS traffic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1893650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
