Memory leak in browser and Deezer desktop app

The same behaviour in Google Chrome. IMHO, as this is a web access app, it should work without serious issues in any browser following HTTP standard. I wouldn’t expect company like yours can afford to ignore Linux platform as a whole. You indirectly limit your user’s freedom of choice.

same issue here, if I use web deezer player in firefox, it consumes all memory I have in half a day

mce@mcl2:~$ uname -a
Linux mcl2 5.3.0-45-lowlatency #37-Ubuntu SMP PREEMPT Thu Mar 26 21:30:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
mce@mcl2:~$ cat /etc/issue
Ubuntu 19.10 \n \l
mce@mcl2:~$ apt show firefox
Package: firefox
Version: 74.0+build3-0ubuntu0.19.10.1

When can we expect this to be fixed?

It has been going on for a long while, and nothing seems to have changed. This is extremely annoying and constantly breaks Deezer in the browser. I think it would be fair to state that we should have seen this fixed years ago, we pay a monthly subscription to use the service after all.

Seconded. Seeing this problem, too. Latest 64bit Firefox, various recent Ubuntu versions, Lenovo Thinkpad, Dell XPS13. Would be nice if the webapp wouldn’t require a restart every couple of hours.

Same problem here! I just want to reinforce the impact of the problem! It does not last more than a half-day to run my computer out of memory.

I’d also like to add my 2 cents to this. The memory leaks happen a lot on my Arch Linux system regardless of what I use. Firefox, Vivaldi (Chromium-based), MellowPlayer (Chromium-based music streaming wrapper) and the unofficial Linux port of the desktop app. Most of the time it just uses about 2 GB of RAM, which is still way too much, other times it fills up my entire RAM even when just browsing an artist page.

I tested on Chrommium 88 and it seems to be fine. I did a little more digging into the memory snapshot and found “memory-file-data/string” is “Memory used to back a File/Blob based on a string”. In the snapshot above, it would have been ~10274 ~524KB chunks of blobby memory. Haven’t figured out how to dig further or do a clean up, but was wondering if they are stayin around if you are calling createObjectURL on Blobs/Files/MediaSources without then calling revokeObjectURL on them. Also noticed https://developer.mozilla.org/en-US/docs/Web/API/URL/createObjectURL#using_object_urls_for_media_streams which might be valid for you ¯\_(ツ)_/¯

I know you are working on a new and improved interface, but fixing this bug would make the current one not have to be closed and refreshed every couple of hours.

Just did a quick test to replicate it in FF (ran in console)
 

const part = 'zzzzzzzzz ';
let big = '';

for (let i = 0;i < 52000; i++) {
  big += part;
}
// Take memory snapshot (60MB)
// Try making blobs without url
for (let i = 0; i < 400; i++) {
  const blob = new Blob([big], {type: 'text/plain'});
}
// Take memory snapshot (60MB)
// Make blobs with urls
let urls = [];
for (let i = 0; i < 400; i++) {
  const blob = new Blob([big], {type: 'text/plain'});
  urls.push(URL.createObjectURL(blob));
}
// Take memory snapshot (260MB)
// Clear URLs
urls.forEach((url) => URL.revokeObjectURL(url))
// Take memory snapshot (60MB)

Sure thing! @Dagrut 

That's really nice feedback from you.

Yes, and we've made some progress internally this week. Things are a bit slow but all going well.

Our current app has had a big update as well, to version 5.0, and I noticed the performance improved. Looking forward to what's coming next 

I'll keep your name on the radar for future testing too 

@Rudi It happens when I play Flow, but also when playing playlists (loved tracks in my test)

I’ll try Discovery / Chill cards tomorrow

The memory growth is very slow FYI, it takes a few hours to go up to up to a Gigabyte of memory (for example I’m at 350Mb after about one hour, starting from ~ 120Mb initialy)

It only occurs when playing, I have the tab kept open all night without any change

I would like to share related discussions:

• https://bugzilla.mozilla.org/show_bug.cgi?id=1591722
• https://www.reddit.com/r/deezer/comments/g9aur8/mac_desktop_app_high_memory_use_common/
• https://github.com/ColinDuquesnoy/MellowPlayer/issues/169

This problem seems to be annoying everyone that plays Deezer on PC for many hours

Hi @Richard B. Kreckel, appreciate your opinion. In all honesty, it actually sounds we're going back to basics and improve the player as a whole, from scratch, not trying to fix a patch that may not offer a solution in the long term. One of our big focuses this year is to improve reliability, and that's why I suggested you to stay tuned for further updates.

Take good care and have a great week!

I’ve also been experiencing this for years now, and it’s super annoying. I’m really surprised this has not been fixed yet.

As far as I understand this happens in the browser player, in any browser on any platform.

@developers It likely has something to do with the decrypted track cache. Make sure you explicitly clean this up after playing a track, the browser won’t do that for you.

This would also be a reason for me to switch to a different service.

Good luck!