Bugzilla – Bug 1221314
[Build 630.1] firefox has a problem with 4GB on aarch64
Last modified: 2024-03-27 08:19:49 UTC
## Observation To sum up the situation firefox is killed by OOM killer on a Leap 15.6 Beta / GNOME 45 / aarch64 box with 4GB in openQA. Mar 11 20:41:30.691185 susetest kernel: firefox invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=100 Mar 11 20:41:30.881008 susetest kernel: CPU: 0 PID: 4245 Comm: firefox Tainted: G n 6.4.0-150600.9-default #1 SLE15-SP6 3c8e733979fdbcdb4a6e86e1f33921ba7364d90b` Similarly it is super slow on Plasma 5.27 (again in openQA) but doesn't get to the point that OOM would kill it. In comparison chromium works on a machine with 2GB ram. openQA test in scenario opensuse-15.6-DVD-aarch64-gnome@aarch64 fails in [firefox](https://openqa.opensuse.org/tests/4006074/modules/firefox/steps/29) This started to happen with our last 15.6 build 630.1. The problem with 4GB is that this is our currently recommended minimum. I'm afraid that we'd have to change if SLES's default desktop and browser would be unusable with 4GB. ## Reproducible Fails since (at least) Build [601.1](https://openqa.opensuse.org/tests/3923052) ## Expected result Last good: [597.1](https://openqa.opensuse.org/tests/3902961) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensuse&flavor=DVD&machine=aarch64&test=gnome&version=15.6)
Actually I'm wrong https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-x86.html#:~:text=A%20minimum%20of%201024%20MB,FTP%2C%20add%20another%20150%20MB. we do state that 3GB of RAM is a minimal requirement for desktop. So 1GB less than when we currently hit the issue with firefox.
Assuming this opoenQA test is running Firefox 115esr, this Firefox requires a minimum or 2GB of memory and 200MB of disk space. What is the memory usage on this machine before the Firefox run and after it fails?
https://bugzilla.suse.com/show_bug.cgi?id=1220316 I think it's the same bug. Not related with firefox directly, but it's speech-dispatcher.
Fixed in build 641.1: https://openqa.opensuse.org/tests/4038692#step/firefox/34