![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 10/08/2020 15.41, James Knott wrote:
On 8/10/20 8:51 AM, Carlos E.R. wrote:
I have killed Firefox many times, even before this issue, so I'm quite familiar with that. However, it seems to be more related to Chromium.
No, I'm not saying "kill Firefox" (nor Chrome), but kill "Web Content". Different thing.
Some of the pages you load causes that.
The pages I load haven't changed much from what I've been using prior to this. In fact, just looking at the list, there is nothing that I haven't been reading since well before this particular issue.
I tried killing Web Content and it made no difference. However, the problem does appear to be related to Chromium. I normally run Google GMail, Calendar, Contacts and Messages in 4 tabs all the time and have Chromium configured to open all 4 when I start it. After I start it, I can see the CPU usage go to max on all 8 cores and then when I kill, things go back to normal. I have been using Chromium that way for years, yet this problem just started very recently. IIRC, there was a Chromium update recently. The thing is, it doesn't always go to max when I start Chromium. I just started it now and everything looks normal, but the problem happened when I started it a few minutes ago. I'm currently using about 5 GB of memory out of 16 and no swap. This is typical of when the problem happens. CPU is currently very low (a few percent) on all 8 cores.
Ok, so you have four tabs. Killing "Web Content" should kill _one_ of those 4 tabs. Which? Explanation. Web browsers now start several threads - for example, Firefox seems to start 8 by default, and distribute the tabs evenly between those threads. So if you have 4 tabs only, killing one thread should kill one tab. Which tab? There is some broken web page in that tab. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)