On 8/10/20 2:05 PM, Carlos E. R. wrote:
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.
I didn't check which tabs. However, those 4 Google pages were in Chromium, not Firefox and killing Web Content seemed to work on Firefox only. I'll have to try again next time it bogs down. It seems to be OK right now, with all cores bouncing around 10% or so and 4.5 GB of memory used and no swap. BTW, I tried in my test account with only a browser running a single tab & speedtest.net. Firefox was a bit poorer than normal and Chromium was much worse. I typically get low 90s down, but got upper 80s down with Firefox and about 7 with Chromium. This was on a freshly booted computer, running only the browser and System Monitor running. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org