This is pretty much what I think. Can't vouch for it, of course. But the
choking up to no reaction only happened yesterday. As usual, in the
beginning I expected some tab to require lot of CPU time. Therefore, I
use the widget shown in the image relatively frequently. And sometimes I
close a demanding tab. So this belongs to my almost staple diet.
Yesterday, again, I wanted to find out if I had en extremely demanding
tab, when I noticed, to my surprise, that the CPU was hoovering around
2-5 percent. That was the first time I noticed. Closed Chrome, opened
Chrome again, same. Logged off, logged in, same. Cold boot, same.

Attached you'll find the image of the resources with Firefox, only
running application, after some 5 hours of running, some 20 tabs, the
same that I use daily on Chrome. And it looks similar to what it used to
look throughout the last years, using Chrome. And it looks like what one
expects.

** Attachment added: "Normal resource use, as earlier and here with Firefox"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+attachment/5607144/+files/Screenshot_20220805_160001.png

-- 
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/1983660

Title:
  Chromium seems to drive all data into swap, until choking

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  For the last day(s) my machine runs Chrome very very slow and sluggish until 
it stops reacting at all. I haven't done any changes except of the daily 
updates and snap refresh. 
  What I found out, is that the memory space used is almost immediately the 
swap space. Same after cold boot: it starts pretty usual, but soon almost all 
memory data seem to be sent into swap space, despite of RAM being available. 
(See attachment, taken shortly before total non-reaction. CPU isn't very busy, 
RAM is aplenty.)

  Swappiness is okay at 60. 
  I very much suspect Chrome, since when using Firefox, with my (in Chrome) 
usual sites, everything looks fine, it doesn't choke, and the swap space used 
is almost negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to