More > JRiver Media Center 26 for Linux
JRiver on Raspberry Pi has a memory leak?
mwillems:
Under media network-->client options there are three options. Are any or all of those checked? If so, try unchecking the sync library automatically (or something like that) check box.
I've had a longstanding memory leak in client server situations with that option checked; every time the client syncs the library a little more memory is used until the client crashes. It presents exactly like what you're seeing. I can reproduce it instantly just by clicking the refresh view button in standard view, but bob hasn't been able to reproduce it, so I assumed it was some idiosyncrasy of my network. I see it with all linux clients, not just raspberries, but it's much more obvious on raspberries because of the limited RAM.
Try disabling that option and see if that's your issue.
DrKNo:
--- Quote from: mwillems on January 22, 2020, 01:37:10 pm ---If so, try unchecking the sync library automatically (or something like that) check box.
--- End quote ---
That did it! RAM usage increases with a new song, but is freed after the song ends, MC is now stably using ~270MB of RAM for half an hour, it usually would have been in the sixhundereds now. Thank you so much! I suppose library sync is unnecessary for me anyway since I am using the raspberry PIs as playback endpoints only.
--- Quote from: JimH on January 22, 2020, 01:20:17 pm ---What are you playing?
--- End quote ---
FLAC and MP3. FLACs might have seemed to increase the RAM usage more, but I would have to verify.
I'm happy to investigate/contribute if possible. Jim, I could send you an SD image if that helped? My server is reachable from the Internet, so we could even test that.
JimH:
We'll take a look. Thanks, mwillems.
bob:
Are you running 26.0.19?
I'm going to upload a new build with a fix for that so when you see it if you could test it with library sync back on that would be good.
Thanks.
DrKNo:
Happy to. Update it both on server and on RasPi? I'm not sure I get to test it before Wednesday, but I'll try my best. What build number should I check? Or did you mean I should test 26.0.19?
Edit: Nevermind, saw the fix in 26.0.20, I'll report as soon as I get the chance.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version