Memory leak in browser and Deezer desktop app

Hi there @mce 

Thanks for coming back to us.

We're unhappy about not supporting Linux at the moment so we understand your frustration - apologies we're unable to give you the integration you've been looking for.

It's just at this moment, this kind of development requires resources that are dedicated to more urgent features and fixes. This situation is likely to change in the future, but we also want to be transparent with you and the rest of the community. Follow this topic here for more info, some users shared their workarounds and there might be something for you 

Hi all, 

I’m having the same problem: when deezer in a browser is playing songs, the memory footprint of the browser process grows and grows, making it infeasible to enjoy deezer. This is on all my browsers (Chromium, Brave + Vivaldi (which both rely on Chromium), and Firefox (which does not)), ran on Linux Mint. 

I know you «don’t support Linux» but since the problem persists in several browsers, and arnaudd_fr reproduced the problem on Windows 7, there is evidence that this is not a Linux issue but a problem of the deezer browser app. 

Either way, I find this very frustrating - it makes deezer unusable on the desktop for me. Please make an effort to fix this, it has been two years with this problem now. 

best wishes

Kai

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.

Hey @Mateus Amarante @tobert 

I get you, really. Sorry to hear about your experience.

Could I please ask you to vote for this idea here (if you haven't already done so) and check if you can install an unofficial version of the desktop app for your Linux 

In the meantime I'll be forwarding your comments to our teams 

Bug confirmed with Firefox 78.0.2 - 64 bits under Ubuntu 20.04LTS.

As a french user, I recently changed to a hifi account and the memory leak is now extremely quick to take down the whole system memory (8Go+2Go swap) and crash/freeze the browser (in less than 2 hours of listening).

So the leak seems proportional to the selected audio quality. This problem is terrible and does not happen with other audio streaming providers i have tested. So this is probably not a linux-specific related issue.

Please fix it ASAP.

Hi @j94,

Really sorry to hear about it. Our team is already aware of the issue and are working on it.

On the other hand, would you be able to try it on Chrome and see if that works out better for you by any chance? 

Hi.

I confirm the bug on Xubuntu 20.04, in Firefox and Chromium.

Need to refresh the tab sometimes to clear memory usage.

I use Chrome OS and no issue like this.

Have you tried to reinstalling browser. I must be extremely lucky, but nothing like this.

It played for hours now on my Chromebook during the work day and the evening.

On my three week journey with Deezer I can’t find anything big. The ones I do find need work, I’ve took moments to surf on this community and most of this are either in the fix or coming.

Isn’t Chromium almost the same as Chrome and Chrome OS?

The web version, since is played by browsers that are “almost” the same in windows and linux are “ supported” in a indirect way by you. So please, don’t give that risponses because we are using Linux because it’s much probably that is happening in windows too.

Actually, I have noticed this in the electron, official, native app version too( app version of windows, that is avalaible in Linux with some tweaks). The memory is being increased by the time you are using the player.

But with more hours is worse, the app increase them memory ram usage until “ no” limits, because I have seen deezer using 0.7 GB itself so… Electron is deezer by itself because deezer is build with electron at some “ easy” way to say, you can ask your developpers.

To sum up,. the app is getting more memory like the playing time is higher.

So in little words, this is likely to happen too in windows, and I think is not so high priority but this has to be addresed in some time… ( in browser and app versions, both)