When I first start it:
After a bit under 24 hours, half playing and half idling in the background:
It keeps going up if I let it stay running - about 1gb every 24 hours on my box (imac pro, intel, ventura).
Unused memory is wasted memory!
(kidding, mostly)
If you can share them, Plexamp logs might tell some of the story. We periodically log about memory usage while the app is running.
1 Like
Good thing plexamp is not wasting any of my memory!
Sending you my Plexamp.log.zip for the past couple days via DM.
You see anything usable in the logs I sent you?
You ever see the old movie “The Blob”?
Nothing particularly telling in those logs. In fact, it’s showing only very little memory usage 
I’m not a macOS user, so I’ll ask around and see if anyone else has any ideas.
Interesting. So I guess it looks from the log like the js memory usage is pretty flat and pretty economical. There must be something else in the bundle that is leaking. It looks like plexamp is an electron app… electron can be… problematic (and bloated). And there is a bundled treble framework and I assume also a bundled node install to make all the js work.
Due to the apparent memory leak, I quit and restart plexamp whenever i think about it. It’s been probably 24 hours since the last restart and the activity monitor on my mac is telling me this:
Drilling into the particulars of Plexamp memory usage shows me this:
I haven’t been able to find anybody else who can reproduce this, and I’ve seen no other reports of it. Makes it hard to find a pattern or root cause.
The next version of Plexamp includes a lot of under the hood changes that might make a difference to memory usage. Let’s hang tight and see if it’s still happening once that release is out (shouldn’t be too long now).
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
