include
Answered

Memory leak in browser and Deezer desktop app



Show first post

99 replies

Hi there,

Suffering from massive memory leaks on Mac ; 1.75Gb usage, more so than Adobe Photoshop being used in parallel. Problem resolved on reboot of desktop app, but very frustrating having to periodicially restart it all.

Userlevel 2
Badge

Performance-wise there's a long road to go @bytesnz, that makes sense.

This feedback is always important - could you please confirm you're on version 4.32?


Apologies the memory stats are for the web app (FF being Firefox). Will try in Chromium and see if I have the same issue.

Userlevel 7
Badge +7

This will be something we're tackling in the long-term @Rhazkept so thank you very much for your feedback, it's super useful :thumbsup_tone2:

Hi.

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

Need to refresh the tab sometimes to clear memory usage.

Userlevel 7
Badge +7

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 :nerd:

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

Userlevel 2
Badge +1

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. 

Userlevel 7
Badge +6

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.

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.

I also report the bug. it doesn't make sense, after a few hours Deezer can easily be consuming 6GB of RAM, I'm using the HI-FI plan. For the desktop version in windows, with the music already downloaded it consumes 50Mb of network even 100Mb constantly, which does not make sense either.

Badge

Hey @Alexey Kapitansky 

Thanks for the honest feedback.

Have you tried the app downloaded directly from us, instead of the store? A fresh install could help you check if the performance is better.

https://www.deezer.com/desktop/download?platform=win32&architecture=x86

Yes, I did. App from MS Store (v5.30.30.0) was leaking and crashing several times per working day. Updated to v.5.30.50.0 a day ago, but haven’t used it enough yet. Will return with feedback.

App v5.30.50.0 crashed. Was listening Flow in HiFi quality.

I add myself into this thread since I also have this issue (and tried reporting it on the french counterpart of this website two months ago but got no response : https://fr.deezercommunity.com/autres-appareils-35/problemes-avec-votre-navigateur-internet-symptomes-et-resolution-15?postid=109210#post109210 ).

I’m running Linux (Debian) with Firefox (but I tried Chromium too), and it usually fills my 16GB of ram in about 6 hours, so I had to add an automatic refresh of deezer tab every 4 or 5 hours.

I’m happy to hear that a new interface is being worked on, I hope it will fix it and other bugs (Cf. link above)!

Also, if there is a way to test it before it’s ready for public release, I bet some people here — including me — would be glad to try it and give feedback.

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.

Userlevel 2
Thanks!
Userlevel 3
Leak easily reproduced on Linux and Windows with Firefox 64

initial state



After 20minutes of "flow"



After 1h of "flow"



For information, all those task manager captures are done with firefox only browsing deezer with "flow" running, nothing else.
Userlevel 3
Same issue has been seen with Linux and reproduced with Windows 7 64 bits.

The screenshots are from windows task manager
Userlevel 7
Badge +7

We totally understand and it's one of our aims to get this much better in the future @Nico S. thanks for the feedback!

In the meantime, our updated app should also improve the RAM usage, so stay tuned :relaxed:

Hello,

I want to report that I also am suffering from the memory leak on desktop (W10). Uninstalling and deleting the folders doesn’t resolve it. App restarts after approx. ±1 hour of playback with RAM usage of up to 6 Gb (that i have seen).

Hardware specs:

  • Monitor: Asus PG279Q
  • MOBO:  MSI B450 Pro carbon AC
  • Prrocessor: AMD R3600
  • Videocard: Gigabyte GTX 1080Ti Aorus Xtreme
  • 16Gb Ram @3600 Mhz
  • Ask away if u need more info

The issue is there since I started my subscription around 2 years ago.

Extra: What is the status on gapless playback?

Regards Glenn

Userlevel 2

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?

Hi Rudi, you keep talking about the desktop app, but this thread is about the leak observed in the web application (on Linux/Windows & Firefox/Chrome). Are the updates are planned for the web app ?

 

That’s great news to know this problem will be solved soon ! Thanks !

 

-- Another french user that needs to reboot its PC because of deezer leaks :( 

Userlevel 7
Badge +7

Hopefully the leak @David Ghitulescu!

We're very close to releasing major updates to our desktop app which should drastically improve the performance of the app! Stay tuned for more updates :relaxed:

Userlevel 7
Badge +7

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:

A long while ago, you said that the developers were on it. Now, “the plans are to improve our player across all apps this year, so we should see an improvement of the performance of our desktop app” unforuntately does not sound like a plan to address the particular problem that has been reported here and confirmed multiple times.

It rather sounds like Deezer doesn’t care about fixing this. Or cannot. Or management has set other priorities.

In the meantime, Deezer keeps crashing browsers and freezing computers.

Would it be possible to hear something concrete and convincing from Deezer apart from vague marketing-speak?

Userlevel 7
Badge +7

Thanks for the detailed feedback @Andriamanitra 

I believe the issue here is the fact we use an Electron package for our app. If it was developed natively, the performance would've been better.

In any case, I've forwarded your comments to our teams :relaxed:

Userlevel 7
Badge +7

Hi @jirikovoego 

At the moment we're unable to develop a different type of app. But we'll keep holding on for different take in the future!

Thank you for your support :relaxed:

Userlevel 7
Badge +7

Hey @pitone176 

Thanks for reaching out about this.

We've got some major updates planned for the desktop app this year and we strongly believe these will sort the RAM issue.

In the meantime, please uninstall the app, remove any Deezer folder you find in %appdata and restart your PC.

After the restart, try installing the app but not from the store:

https://www.deezer.com/desktop/download?platform=win32&architecture=x86

Reply