Memory leak in browser and Deezer desktop app

I have the same problem that everyone here, in my case on the website on Windows 10 with Firefox. I usually stream only for a few hours per session, so it doesn't crash my system, but in the task manager the huge memory usage accumulating on Firefox when I'm streaming on Deezer is very visible.

I do have another very strange problem which I think might also be related somehow to this memory leak issue: Since the end of last year, I can't listen to the longest tracks on Deezer anymore. Whenever a track is over 20-minute long (not something unusual in the genres of music I listen to), after the first 2 or 3 minutes it systematically stops with an error message saying that it can't be loaded. If I manually move the cursor further into the track, the same thing happens again after a couple of minutes. That never happens on shorter tracks, so I guess it's due to the weight of the longer tracks. And in fact, the only way I've found to be able to read those long tracks is to reduce the audio quality, if I put it at only 128kb/s instead of 320kb/s, then it works. But it's not a really satisfaying solution…

I've already talked about this problem on the French forum but no one was able to reproduce it, so I'm left alone with it. I've searched on my side and can't see anything that could explain it (the problem doesn't come from my internet connection or anything), so I think maybe it has something to do with this issue or some related cache overload, but I'm not technically savvy enough to understand how and why. I just thought maybe it could be worth trying to report this problem here, I don't know, but excuse-me if you think it's out of subject.

I've noticed this problem too on Firefox. Switched to Opera browser helped a bit. 

My guess is that the browser keeps the entire stream in ram and doesn't flush between songs. This is why the problem is more evident on the hifi plan. 

Have they done anything about it.

I open Deezer on my Chromebook with 4GB RAM and the computer freezes Deezer web app alone.

It uses all ram in a moment when music started.

So frustrating. I can’t do anything else on the computer.

Other streaming apps work kindly.

I can confirm that I too have this issue when listening to Flow and have had for quite some time. It happens on both Linux (Ubuntu) and Windows 10. I usually use Firefox on Linux and either Chrome or  Edge on the Windows machine so it doesn’t appear to be related to a specific browser. 

No it doesn’t seem to be related to a specific browser (though it might be more apparent with Firefox, according to some reports).
It doesn’t seem to be specifically related to Flow either. Personally I never use Flow, but I have this problem too.

To avoid filling the RAM, I now try to close the Deezer tab after I’ve finished listening to an album, or in between albums, and I don’t leave a Deezer tab opened on Firefox when I’m not using it anymore, like I used to do before when I wasn’t aware of this problem.

But for all those who are still unaware, Firefox has implemented a new workaround in its latest update (version 93.0, released 5 October 2021) which doesn’t solve the problem but could help prevent crashes. I quote from the release notes:
“When available system memory is critically low, Firefox on Windows will automatically unload tabs based on their last access time, memory usage, and other attributes. This should help reduce Firefox out-of-memory crashes. Switching to an unloaded tab automatically reloads it.”

I guess Deezer will be one of the first tabs to be unloaded, for its memory usage is abnormally high. But I was reluctant to mention this here, because I’m afraid that Deezer will take it as an excuse to not do anything themselves, though it’s clear that there is a problem with Deezer specifically.

I have passed all your feedback and concerns to our developers. They are already investigating and well aware of the issue.
I can’t guarantee any permanent fix straight away, but I’ll keep you posted with any update.
Apologies for the inconvenience and you patience is very much appreciated 

Hello friends,

I come to you bearing good news.

The terrible beast of a memory leak has reportedly been slain.

Soon, humble users of the web interface shall no longer fear the dreadful OOM-killer.

https://bugzilla.mozilla.org/show_bug.cgi?id=1591722

Long live the web interface! Long live Firefox! Long live Deezer!

(Chrome users will be sent to the 9th circle of Hell)

Peace

Hallelujah!

I can say that I've been suffering a similar issue for the last few months (beginning some time between late-February and mid-May while I wasn't using it) on the OpenSUSE builds of Firefox - high memory and CPU usage (Goes from 1.2 to 2GB in less than an hour, with the base window taking around 770MB), the search bar becomes unresponsive and both the current track in the window and MPRIS data stops updating after a few tracks, which can inconsistently be refreshed by opening a playlist.

Makes using flow really off-putting as I can't see or interact with whatever track is currently playing.

I would guess it could be caused by a third-party script? I've not tried in a Chromium-based window, is it one of those Chrome-first design issues?