More > JRiver Media Center 21 for Linux
Memory Leak in AMD64 and RPi builds
mwillems:
--- Quote from: bob on October 19, 2015, 04:21:20 pm ---Could you just try looping a mp3 file for local playback? I got a big leak leaving a machine running over the weekend. It might be something about my audio settings too or a leaky audio driver perhaps...
--- End quote ---
Ok good news and bad news:
The bad news: I couldn't reproduce it before because I wasn't running the latest build and didn't realize it :-[ Now that I'm on the latest build I can reproduce the leak. It's easy to see if you're watching a memory monitor. With flac files JRiver's memory usage grows quite substantially on each track change, every single time. You can accelerate reproduction by playing a file waiting a five or six seconds and then skipping forward a track and repeat. I saw memory growth on each skip. A single album got me up to nearly a Gig of memory where MC normally never uses much more than 200M. I should mention I'm also pinging MCWS every five seconds with a script if that contributes (someone else mentioned that above). That was never previously an issue though.
The good news: My being a dope about updating inadvertently resulted in a successful bisect ;D I can confirm that version 21.0.07 doesn't exhibit the memory leak at all for me on Arch, no increase on track change whatsoever. So it's likely been introduced since then.
mwillems:
I think it's new, I have JRiver running on Pi's with 60+ days of uptime that do frequent playback. I've looked at their memory logs and there's no evidence of a leak on that scale (I can post munin-graphs if that would help). Also see my comment over in the amd64 thread, based on my testing I think this came in after 21.0.7.
PrinterPrinter:
I had experienced this memory leak back with MC20 on RPI - maybe there's some conflict in my set up?
My Pi isn't able to play 24 hours without a reboot or a crash ;-) Same behaviour in MC20
Hope this helps,
bob:
Perhaps it's something specific about the options settings.
What are each of your settings for audio playback? (track change settings, stop settings).
bob:
--- Quote from: mwillems on October 19, 2015, 05:34:19 pm ---Ok good news and bad news:
The bad news: I couldn't reproduce it before because I wasn't running the latest build and didn't realize it :-[ Now that I'm on the latest build I can reproduce the leak. It's easy to see if you're watching a memory monitor. With flac files JRiver's memory usage grows quite substantially on each track change, every single time. You can accelerate reproduction by playing a file waiting a five or six seconds and then skipping forward a track and repeat. I saw memory growth on each skip. A single album got me up to nearly a Gig of memory where MC normally never uses much more than 200M. I should mention I'm also pinging MCWS every five seconds with a script if that contributes (someone else mentioned that above). That was never previously an issue though.
The good news: My being a dope about updating inadvertently resulted in a successful bisect ;D I can confirm that version 21.0.07 doesn't exhibit the memory leak at all for me on Arch, no increase on track change whatsoever. So it's likely been introduced since then.
--- End quote ---
Thanks very much. What are your track change settings?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version