include
Skip to main content
Recently, there is a memory leak when using the player in the browser. After closing the tab with the player, the memory returns.

OS: Debian 8.8 amd64 / 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux

Browser: Firefox Quantum 59.0.2 (64-bit)

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.


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?


Hi there, we don't support Linux on the web version, so I'm unable to offer much help, maybe someone else will have some input. In the meantime, there's a topic on our ideas forum about Linux support, make sure you vote for it to be implemented and join the conversation - https://en.deezercommunity.com/ideas/321


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.

 

one hour of playing
recently opened

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)


Hey @Lucas Zorzi

Thanks for the query. We're discussing the possibility of a native app. But in the meantime, could you give us more details about what you've got? OS, browser version, system specs.


Uf, native app sounds me like the final of “not “ oficially supported electron tweaked app for Linux!

So please, be warned, most Linux users ( 670 votes more or less are much users) are going to leave deezer unless they have an app to play music.

 

PD: the native app is efficient, so a good idea I think. But have in mind compability things like Linux one. I think there are much apis that are multiplatform so .. please


Leak easily reproduced on Linux and Windows with Firefox 64

initial state
 

022b1f3e-033f-4862-8ceb-6c624a5b1e3c.png

 


After 20minutes of "flow"

 

4563c7fd-2f13-4b9f-bd42-87e39ec52acf.png

 


After 1h of "flow"

 

9de8ce5c-00e6-4d05-8811-454e045793fb.png

 


For information, all those task manager captures are done with firefox only browsing deezer with "flow" running, nothing else.

 


can you see if in the app it occurs too or not please? at least for me in linux with aur package is happening so I think it will be in windows to.


@Rudi can we change title ( too “ memory leaks on browser and app”)once a time it’s confirmed that windows app ( in windows) is having the same problem with memory leaks? For me in Linux is happening and this is probably a windows too problem so..


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? 

I tried this morning with latest Chrome stable (debian package) : 84.0.4147.89 (Build officiel) (64 bits).

Chrome displays the same behavior, with the ever-growing memory usage being tied to the deezer tab (and not to the chrome parent process which remains stable). Notes :

  • the memory gets freed when closing the tab.
  • the memory loss is much quicker with “hifi” setting than with MP3 (128 or 320) setting.
  • pausing playback has no effect (does not free the memory) neither has finishing or emptying the playlist with playback “naturally” coming to a halt.

Thoughts : the memory leak may be tied to the improper implementation of some kind of client-side library or middleware (used for caching, unpacking or sound processing ?) that needs explicit (maybe undocumented ?) memory management not being called by deezer.


@Alblinux I took care of it.

Thanks for the precise feedback @j94, we’ll forward it to the dev team. I’m sorry we didn’t have the time to take a closer look to this issue so far.


I also have this problem both on Linux and Windows. Firefox (the deezer tab) sometimes takes all of the available memory in my system, causing the entire system to hang and crash.

After closing the tab the memory is released.


Hey @Bram D

We don't fully support Linux yet - the development of an app is on the plans, but we still need more time. Could I kindly ask you to try Deezer on Chromium to see if the leak is similar? Thank you for keeping us updated :v_tone2:

On Windows do you also use Firefox?


I would like to share related discussions:

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


Thanks for highlighting the other channels @Mateus Amarante you've got a point :thumbsup_tone2:

I'll be sharing the links with the teams to make them aware.


AFICT, this is specific to Deezer. I can reproduce this on Linux Firefox 81.0, Vivaldi 3.3.2022.47 and Chrome 85.0.4183.121, also under Windows using an older version of Firefox. With all theses browsers there is flat memory consumption with e.g. TuneIn.


Thanks for reviewing this in detail @Richard B. Kreckel our devs are aware so I just added the specs of the browsers you mentioned, for a complete report on this :thumbsup_tone2:


Hey @Bram D

We don't fully support Linux yet - the development of an app is on the plans, but we still need more time. Could I kindly ask you to try Deezer on Chromium to see if the leak is similar? Thank you for keeping us updated :v_tone2:

On Windows do you also use Firefox?


Hey Rudi,

I’m not talking about a native app, but the Deezer web app. On Windows I also use Firefox (latest version). I’ll try it on Chromium and let you know the results. However I would very much like to see this fixed ASAP for Firefox.

Since the memory usually increases a couple of megabytes per song that is played, I suppose the songs are not properly removed from memory after playback?


Hey @Bram D 

Gotcha! Thank you for coming back and explaining.

Realistically (and so that we're transparent with you), if we dedicate resources to this, we'd be more inclined to get a native app done - so that's easier to support, instead of working with different browsers. Either way, I'll be more than happy to pass on the feedback to our developers :wink:


What are Deezer’s plans to fix this clear cross-platform and cross-browser memory leak? Would it, please, be possible to keep the community posted?

This issue has been reported more than two years ago. Unfortunately, no fix has appeared since then. Is it impossible to fix this? Some users need to choose between upgrading RAM significantly or switching to another service! But most users are probably in the dark about why their machine behaves badly (web browser freezes, crashes). A native client has been proposed repeatedly. But remember that a native client may not solve this for everybody -  the most portable thing is and remains a web service.


Hi @Richard B. Kreckel 

Thank you for your reply and for your support.

We're working on it. It took some time to prioritise the project which is really going to fix the root cause of the RAM issue, but it's on its way now.
We have close contact with the devs working on it :thumbsup_tone2:

We're on it and really sorry for the inconvenience, we really want to see it fixed :v_tone2:


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!


Thank you for also sharing your feedback here @timvisee will pass it on :thumbsup_tone2:


Recently, there is a memory leak when using the player in the browser. After closing the tab with the player, the memory returns.
OS: Debian 8.8 amd64 / 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux
Browser: Firefox Quantum 59.0.2 (64-bit)

All answers from the Deezer Stuff show that no one of them read all comments. 
It’s not a problem of Ubuntu or linux. Same problem exist with windows.
There ist problem with deezer in any browser on WIndwos and Linux!


Recently, there is a memory leak when using the player in the browser. After closing the tab with the player, the memory returns.
OS: Debian 8.8 amd64 / 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux
Browser: Firefox Quantum 59.0.2 (64-bit)

All answers from the Deezer Stuff show that no one of them read all comments. 
It’s not a problem of Ubuntu or linux. Same problem exist with windows.
There ist problem with deezer in any browser on WIndwos and Linux!

and in the app of windows. Mac I don’t know to be honest but in windows it has to be too...


Hey @Peter5411 @Alblinux 

Part of our big focus for 2021 is to improve our desktop app a lot. Please bear with us, we know it hasn't been as smooth as it should be :pray_tone2:


Reply