Memory issues while listening to music on deezer.com using Falkon and Firefox

aquatic

aquatic

Summary
When listening to music on deezer.com in, the system allocates more and more memory. If I do not close and reopen the tab after some hours, the memory runs full and the system gets slow and the unresponsive (Before edit, I wrote "system crashed" which was imprecise).
This happens in Falkon and Firefox.

On Windows 11 in Firefox, no such issues occur.

Because it happens in two different browsers on FreeBSD and not on Windows 11 in Firefox, I guess it is related to FreeBSD.

Details on the memory usage (music quality "HiFi")
In the first test, I set the music quaity to "HiFi".

Queried using the following command:
ps -aux | grep -E "falkon|QtWeb"

Time/usr/local/bin/falkonQtWebEngineProcess: --type=rendererQtWebEngineProcess:
--type=utility
--utility-sub-type=audio.mojom.AudioService
14.26 p.m. (before playing)VSZ: 901'728 KiB
RSS: 416'540 KiB		VSZ: 17'306'984 KiB
RSS: 320'856 KiB		not existing
17.38 p.m. (after playing music for 3 h 12 min)VSZ: 998'652 KiB
RSS: 383'152 KiB		VSZ: 18'907'520 KiB
RSS: 1'843'708 KiB		VSZ: 341'952 KiB
RSS: 103'592 KiB
21.39 p.m. (after playing another 3 h 1 min)VSZ: 997'884 KiB
RSS: 204'076 KiB		VSZ: 20'535'512 KiB
RSS: 3'327'824 KiB		VSZ: 346'176 KiB
RSS: 67'348 KiB


Details on the memory usage (music quality "standard")
In the second test, I set the music quaity to "standard".

Queried using the following command:
ps -aux | grep -E "falkon|QtWeb"

Time/usr/local/bin/falkonQtWebEngineProcess: --type=rendererQtWebEngineProcess:
--type=utility
--utility-sub-type=audio.mojom.AudioService
21.51 p.m. (right after start playing the music)VSZ: 1'086'952 KiB
RSS: 486'004 KiB		VSZ: 17'374'020 KiB
RSS: 367'260 KiB		VSZ: 346'176 KiB
RSS: 59'204 KiB
07.57 a.m.
(after playing music for 10 h 6 min with std quality)		VSZ: 1'078'760 KiB
RSS: 326'192 KiB		VSZ: 17'979'860 KiB
RSS: 957'700 KiB		VSZ: 346'176 KiB
RSS: 59'144 KiB
11.35 a.m.
(after playing music for another 3 h 38 min)		VSZ: 1'082'856 KiB
RSS:
359'852 KiB		VSZ: 18'192'264 KiB
RSS: 1'171'920 KiB		VSZ: 346'176 KiB
RSS: 591'56 KiB

Details about the system
uname -mrs: FreeBSD 13.2-RELEASE amd64
It runs on a QEMU VM (machine "Q35-7.1", bios "OVMF")

Next steps
Before I create a bug report, I would be grateful if someone could try to reproduce this issue on deezer.com.
Also if you have an idea what I could check to find the root cause, please let me know!
 
What does “system crashes” mean?

Unresponsive, powers off, reboots? Firefox crashes and/or X? Or some sort of freeze?

And this is all under QEMU so not real hardware? Just checking that’s the case.
 
System crashes means that it freezes the moment the memory runs full and some minutes later it gets completely unresponsive, sometimes it does not even show anything on the screen.

This is all under QEMU, yes.
 
aquatic said:
System crashes means that it freezes the moment the memory runs full and some minutes later it gets completely unresponsive, sometimes it does not even show anything on the screen.
Click to expand...
That's not a crash. That's simply the result of resource starvation. How much memory does the guest have? And how much swap is configured? And did you do the test with Windows 11 on the same kind of QEMU VM? Or is that running on bare metal?
 
The guest has 8 GiB memory, swap is also 8 GiB.
The latest test I did on a bare metal Windows 11, but I have been running a VM on Windows 11 on a similar QEMU VM. There I could listen to deezer.com without the memory got filled up.
 
linux-browser-installer does not include Firefox, so I installed Chrome as Linux browser to repeat the music playing test.

In Chrome as Linux browser, deezer.com showed an error on selecting the profile which translates to "You do not seem to have an internet connection". I could overcome this issue by reducing the performance to "slow 3G" in the DevTools while selecting the profile. Also on loading the music, there were error messages as long as the performance was not reduced in the DevTools.

Test results on playing music in Chrome as Linux browser:

ps -aux | grep -E "chrome" on 9.53 a.m.

Code: 
aquatic    13278   1.0  3.7 1188029676 306640  -  S    09:04       0:22.76 /compat/ubuntu/opt/google/chrome/chrome --type=renderer --crashpad-handler-pid=0 --enable-crash-reporter=,unknow
aquatic    13264   0.0  0.0      13584   2292  -  I    09:04       0:00.01 /bin/sh /usr/local/bin/linux-chrome
aquatic    13269   0.0  2.5   34106888 212076  -  S    09:04       0:15.21 /compat/ubuntu/bin/chrome --no-sandbox --no-zygote --test-type --v=0 (Chrome_DevTools)
aquatic    13272   0.0  0.0   33578204   2260  -  I    09:04       0:00.01 /compat/ubuntu/opt/google/chrome/chrome_crashpad_handler --monitor-self --monitor-self-annotation=ptype=crashpad
aquatic    13274   0.0  0.0   33569992   2160  -  I    09:04       0:00.00 /compat/ubuntu/opt/google/chrome/chrome_crashpad_handler --no-periodic-tasks --monitor-self-annotation=ptype=cra
aquatic    13276   0.0  1.6   33905848 132128  -  S    09:04       0:19.42 /compat/ubuntu/opt/google/chrome/chrome --type=utility --utility-sub-type=network.mojom.NetworkService --lang=de
aquatic    13277   0.0  1.5   33888660 128072  -  S    09:04       0:00.14 /compat/ubuntu/opt/google/chrome/chrome --type=utility --utility-sub-type=storage.mojom.StorageService --lang=de
aquatic    13281   0.0  2.5   34126712 211020  -  S    09:04       1:01.95 /compat/ubuntu/opt/google/chrome/chrome --type=gpu-process --no-sandbox --v=0 --crashpad-handler-pid=0 --enable-
aquatic    14749   0.0  1.6   34040988 129400  -  S    09:19       0:00.80 /compat/ubuntu/opt/google/chrome/chrome --type=utility --utility-sub-type=audio.mojom.AudioService --lang=de --s
aquatic    14920   0.0  1.6 1185771620 134108  -  I    09:51       0:00.06 /compat/ubuntu/opt/google/chrome/chrome --type=renderer --crashpad-handler-pid=0 --enable-crash-reporter=,unknow
root       14924   0.0  0.0      12816   1988  1  S+   09:54       0:00.00 grep -E chrome

ps -aux | grep -E "chrome" on 12.52 a.m.

Code: 
aquatic    13278   1.0 18.9 1188045776 1575368  -  S    09:04       9:15.14 /compat/ubuntu/opt/google/chrome/chrome --type=renderer --crashpad-handler-pid=0 --enable-crash-reporter=,unkno
aquatic    13264   0.0  0.0      13584    2292  -  I    09:04       0:00.01 /bin/sh /usr/local/bin/linux-chrome
aquatic    13269   0.0  2.6   34102788  212928  -  S    09:04       0:52.50 /compat/ubuntu/bin/chrome --no-sandbox --no-zygote --test-type --v=0 (Chrome_DevTools)
aquatic    13272   0.0  0.0   33578204    2260  -  I    09:04       0:00.01 /compat/ubuntu/opt/google/chrome/chrome_crashpad_handler --monitor-self --monitor-self-annotation=ptype=crashpa
aquatic    13274   0.0  0.0   33569992    2160  -  I    09:04       0:00.00 /compat/ubuntu/opt/google/chrome/chrome_crashpad_handler --no-periodic-tasks --monitor-self-annotation=ptype=cr
aquatic    13276   0.0  1.6   33905848  132032  -  S    09:04       1:36.77 /compat/ubuntu/opt/google/chrome/chrome --type=utility --utility-sub-type=network.mojom.NetworkService --lang=d
aquatic    13277   0.0  1.5   33888660  128096  -  S    09:04       0:00.41 /compat/ubuntu/opt/google/chrome/chrome --type=utility --utility-sub-type=storage.mojom.StorageService --lang=d
aquatic    13281   0.0  2.6   34130440  215400  -  S    09:04       2:29.07 /compat/ubuntu/opt/google/chrome/chrome --type=gpu-process --no-sandbox --v=0 --crashpad-handler-pid=0 --enable
aquatic    14749   0.0  1.6   34040988  129412  -  S    09:19       0:31.45 /compat/ubuntu/opt/google/chrome/chrome --type=utility --utility-sub-type=audio.mojom.AudioService --lang=de --
aquatic    14950   0.0  1.8 1185771620  151352  -  I    10:06       0:00.09 /compat/ubuntu/opt/google/chrome/chrome --type=renderer --crashpad-handler-pid=0 --enable-crash-reporter=,unkno
root       15364   0.0  0.0      12816    2024  1  S+   12:52       0:00.00 grep -E chrome

The RSS of the first process rised from 306'640 KiB to 1'575'368 KiB within 3 hours. The rising memory also occurs on Chrome on Linux.
 
Update: I played music on deezer.com for several hours (16 h or more) several times in Chrome on Linux. The amount of memory used increases, but shortly before the system runs out of memory, the Chrome for Linux process reduces the amount of memory used.
 
You must log in or register to reply here.
Back
Top