More > JRiver Media Center 26 for Linux
JRiver on Raspberry Pi has a memory leak?
bob:
Would you all give 26.0.22 a try please?
Mike Noe:
I hadn't noticed this issue on my Pi4 here, but pre-22 it was starting at about 90MB and after a few hours would hit 200MB, then hold there.
With 22, it starts about the same, but after a couple of hours, tops out at 110MB, same playback/connection conditions. So that looks nice. ("RSS" number from the Raspbian Task Manager)
This is with two or three MCWS clients polling and whatnot, with the Pi (running Raspbian) playing back to just one USB Audio device (zone) with a fairly light DSP setup (Output Format/Volume Leveling/Adaptive Vol/Equalizer).
DrKNo:
Raspberry PI on .22 shows the same behaviour for me (Server is .18, Windows 10). No DSP on the Pi, RAM usage stops rising once AutoSync is deactivated.
bob:
Ran 26.0.22 overnight on a Pi4 with sync on and it stabilized at 180MB before I left yesterday and is still at that (and has been playing continuously since then) this morning.
If anyone is still seeing memory rise, more details are going to be necessary.
mwillems:
22 seems a better for me in preliminary testing. I can still force big spikes in RAM usage by mashing the refresh button repeatedly, but some/most of the RAM gets released later. Ditto with rapid view changes.
I can get RAM usage to stick up at around 1G on my amd64 systems, but no higher even after extended playback. On armhf, jriver uses about 200MB before I play anything, I could force the pi up to around 500MB (via refreshing and view switching) but it would sink back down to 400MB at steady state, and I couldn't immediately get it much higher or to trigger the OOM killer.
That's a big improvement so far. I plan to leave a system or two playing overnight to see if there's still a slow leak, but so far so good here.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version