Could some Chromium users report whether it is working or whether it crashes the whole system due to OOM. Seen 4 reports of this on Reddit. -- Callum Farmer gmbr3@opensuse.org openSUSE/GitHub/GitLab - gmbr3
On 7/5/21 2:02 PM, Callum Farmer wrote:
Could some Chromium users report whether it is working or whether it crashes the whole system due to OOM. Seen 4 reports of this on Reddit.
I'm running chromium under XFCE4 (X server, no wayland) with HW acceleration disabled. Before a recent Tumbleweed updates shipping a chromium update it crashed all time when closing chromium. Currently (chromium-91.0.4472.114-2.1.x86_64) it spits out some ERROR messages to terminal during stopping. I wouldn't call that stable. :-/ Ciao, Michael.
Hello, On Mon, Jul 05, 2021 at 01:02:44PM +0100, Callum Farmer wrote:
Could some Chromium users report whether it is working or whether it crashes the whole system due to OOM. Seen 4 reports of this on Reddit.
I have 8GB of ram most of it taken by Chromium, Firefox, and Evolution. It does not crash but sometimes there is big memory pressure leading to stalls until I close some tabs with 'web application' style pages. When that happens the browsers also sometimes actively flag random pages as 'unresponsive' offering to terminate the related processes. All in all I think it should not happen. I am using Tumbleweed on this small machine. With Leap I see no problems either but there is much more RAM available, too. Thanks Michal
A while ago, I also was suffering from serious "unresponsiveness" when opening moderately-large Google Spreadsheets. After reading an earlier version of https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuni... <https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuning-memory.html#cha-tuning-memory-vm>, I found that setting: sysctl vm/watermark_scale_factor=1000 from its default value of 10 greatly improves performance in these situations. At first, I was concerned that it would increase swapping/paging, but it does not. All it does is run kswapd more often to identify free pages. That's additional CPU overhead, but it's not noticeable with today's multi-core systems. I haven't noticed anything negative by making this change. Does anyone have any warnings for me? David On 7/6/21 8:00 AM, Michal Suchánek wrote:
Hello,
On Mon, Jul 05, 2021 at 01:02:44PM +0100, Callum Farmer wrote:
Could some Chromium users report whether it is working or whether it crashes the whole system due to OOM. Seen 4 reports of this on Reddit. I have 8GB of ram most of it taken by Chromium, Firefox, and Evolution. It does not crash but sometimes there is big memory pressure leading to stalls until I close some tabs with 'web application' style pages.
When that happens the browsers also sometimes actively flag random pages as 'unresponsive' offering to terminate the related processes.
All in all I think it should not happen.
I am using Tumbleweed on this small machine. With Leap I see no problems either but there is much more RAM available, too.
Thanks
Michal
On Tue, Jul 06, 2021 at 12:49:18PM -0700, David Walker wrote:
A while ago, I also was suffering from serious "unresponsiveness" when opening moderately-large Google Spreadsheets. After reading an earlier version of https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuni... <https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuning-memory.html#cha-tuning-memory-vm>, I found that setting:
sysctl vm/watermark_scale_factor=1000
Thanks for the tip. Might be worth looking into. The other thing is that some web pages may leak memory, and some web pages are just so huge that they cause OOM or stall the system (huge text files displayed in the browser and NASA photos with excessive resolution come to mind). Michal
from its default value of 10 greatly improves performance in these situations. At first, I was concerned that it would increase swapping/paging, but it does not. All it does is run kswapd more often to identify free pages. That's additional CPU overhead, but it's not noticeable with today's multi-core systems.
I haven't noticed anything negative by making this change. Does anyone have any warnings for me?
David
On 7/6/21 8:00 AM, Michal Suchánek wrote:
Hello,
On Mon, Jul 05, 2021 at 01:02:44PM +0100, Callum Farmer wrote:
Could some Chromium users report whether it is working or whether it crashes the whole system due to OOM. Seen 4 reports of this on Reddit. I have 8GB of ram most of it taken by Chromium, Firefox, and Evolution. It does not crash but sometimes there is big memory pressure leading to stalls until I close some tabs with 'web application' style pages.
When that happens the browsers also sometimes actively flag random pages as 'unresponsive' offering to terminate the related processes.
All in all I think it should not happen.
I am using Tumbleweed on this small machine. With Leap I see no problems either but there is much more RAM available, too.
Thanks
Michal
On Tue, Jul 06, 2021 at 12:49:18PM -0700, David Walker wrote:
A while ago, I also was suffering from serious "unresponsiveness" when opening moderately-large Google Spreadsheets. After reading an earlier version of https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuni... <https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuning-memory.html#cha-tuning-memory-vm>, I found that setting:
sysctl vm/watermark_scale_factor=1000 Thanks for the tip.
Might be worth looking into.
The other thing is that some web pages may leak memory, and some web pages are just so huge that they cause OOM or stall the system (huge text files displayed in the browser and NASA photos with excessive resolution come to mind).
Michal Yes, of course, it's still possible to run out of memory+swap completely. Setting the watermark_scale_factor improves the system's ability to handle large requests for memory that don't exceed that
On 7/12/21 6:11 AM, Michal Suchánek wrote: ultimate limit. You no longer get those long minute or longer episodes of system thrashing. Frankly, I think it should be the default, at least for desktop/laptop systems, as the only downside is a small amount of CPU overhead.
On 12/07/2021 15:11, Michal Suchánek wrote:
On Tue, Jul 06, 2021 at 12:49:18PM -0700, David Walker wrote:
A while ago, I also was suffering from serious "unresponsiveness" when opening moderately-large Google Spreadsheets. After reading an earlier version of https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuni... <https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tuning-memory.html#cha-tuning-memory-vm>, I found that setting:
sysctl vm/watermark_scale_factor=1000
Thanks for the tip.
Might be worth looking into.
The other thing is that some web pages may leak memory, and some web pages are just so huge that they cause OOM or stall the system (huge text files displayed in the browser and NASA photos with excessive resolution come to mind).
Michal
Yes, nowadays 8GB sadly doesn't cut any more, I had to shell out and get 16GB for this old intel i5 4-core machine (DDR3); made a huge difference, since e.g. more ram can be used for disk cache (think grep/rg'ing through huge dirs of text files). Recently I started looking into ways of manually "un-loading" firefox tabs, there are various extensions (I tried "Auto Tab Discard", seems to work), I set to un-load tabs every ten minutes, I tend to have many tabs open (less than 50, for some people many means 100+ :)) in multiple windows, closing a tab sometimes means a thread I intend to read will be lost/forgotten (bookmarking doesn't work that well in such cases), so un-loading the tab seems like a good workaround. I hope that helps. [...] -- Ahmad Samir
participants (6)
-
Ahmad Samir -
Callum Farmer -
David Walker -
James Knott -
Michael Ströder -
Michal Suchánek