Memory and CPU leak on Yosemite

[plmcgrn]

It seems that the most recent update that fixed the issue with Google Music's new design, introduces a nasty CPU and memory leak if you leave it open over time.

I noticed that memory will exceed 1GB in about 48 hours, and CPU will easily be consistently above 30%. When left open long enough, it will overwhelm CPU and easily eat 2-4GB of memory.

[wfortin]

I am experiencing the same issue.

[doque]

Same here:

[Tuinslak]

Confirmed... :)

[mohirt-zz]

..yup :/

[dodgepong]

Same issue here. Activity Monitor reported Radiant Player using over 13 GB of memory this morning after leaving it open for several days. Restarted it and it's back down to ~350 MB, but I expect it to go back up eventually.

[ArtRoman]

OS X 10.9.5, RadiantPlayer consumes memory and CPU after number of uptime days. Old version without material Music was working fine. Spindump says about a lot of operations in JavaScriptCore.
Music in Chrome works great even after some days of uptime without page reloading.

[chumbothewhale]

Same here.

[joeljfischer]

Same as #328

[larouxn]

Issue still persists today. OS X 10.10.4
CPU (I've seen as high as 77%):

Memory:

[ebramanti]

Radiant Player has always had pretty heavy memory usage, but it's becoming unbearable in 1.4.0. Plus with the rollback of @jacobwgillespie's fix, it seems that a lot of these issues might not be fixed for a while.

[dodgepong]

Peronsally I had to switch back to just using a normal browser window + Key Socket Media Keys extension so I could use my keyboard media keys with it. Radiant Player is completely unusable for me on a system where system resources are at a premium.

Honestly I'm started to get tired of there being no good desktop player for Google Music, temping me to move to Spotify, which I'd rather not do.

[serginator]

As @martinlauer stated in #328, if you disable the option Show mini player in menu bar improves a bit the situation, but there's still the memory leak

[krisdestruction]

I think this issue is actually reported in #308

[ebramanti]

Hey everyone,

As part of our Radiant 2 Milestone (more here #409), we are working to improve the performance of Radiant Player. I have begun profiling the memory issue and will let you guys know if I am able to figure out what is causing it.

[krisdestruction]

Should this be closed since it's a duplicate of both #308 and #328 ?

[jacobwgillespie]

Yep, I'll close it as a duplicate of those two other issues.