More > JRiver Media Center 24 for Linux
JRiver Media Center 24.0.28 for Debian Jessie (amd64, i386 and arm)
Mike Noe:
--- Quote from: bob on May 18, 2018, 10:02:04 am ---I ran one all night and the memory usage didn't budge.
Can you try changing the Audio settings to gapless track transitions and uncheck the don't play silence box.
--- End quote ---
Think you're on to something. Changed the transitions to be as you've requested, stopped and started MC, and now, after about an hour, I'm still at "normal" mem usages (~20 MCWS connections, playback on 2 zones)
Do not play silence: Unchecked
Use gapless for seq... : Checked
Use gapless for manual... : Checked
mwillems:
--- Quote from: bob on May 18, 2018, 10:51:44 am ---Thanks for reminding me.
Do you have memory playback enabled?
--- End quote ---
No, memory playback is disabled.
bob:
--- Quote from: Mike Noe on May 18, 2018, 12:03:22 pm ---Think you're on to something. Changed the transitions to be as you've requested, stopped and started MC, and now, after about an hour, I'm still at "normal" mem usages (~20 MCWS connections, playback on 2 zones)
Do not play silence: Unchecked
Use gapless for seq... : Checked
Use gapless for manual... : Checked
--- End quote ---
What was the track transition set to originally? Gapped or crossfade?
bob:
--- Quote from: mwillems on May 18, 2018, 12:10:42 pm ---No, memory playback is disabled.
--- End quote ---
I'm not seeing excessive sockets opened, can you post an example?
mwillems:
--- Quote from: bob on May 18, 2018, 01:16:09 pm ---I'm not seeing excessive sockets opened, can you post an example?
--- End quote ---
Sorry, the sockets were a red-herring I think (I mentioned that down-thread here with some lsof output and other testing results: https://yabb.jriver.com/interact/index.php/topic,115120.msg796478.html#msg796478); one of my pis had lots of extra sockets, but my desktop linux client (which runs amd64) doesn't see extra sockets, but both do see gradually increasing memory usage. So I think the sockets are/were an unrelated issue with my Pi, but the memory leak is real.
So the issue as it currently stands is that all of my Linux clients gradually increase the amount of memory used while "auto-sync with server" is enabled, and don't do so when its disabled (or when there's no client/server connection). The memory growth increases in speed when playing files (predictably on track change), but increases gradually even at idle. The memory growth continues until available memory is exhausted at which point MC crashes. When disabling auto-sync with server, memory growth stops but existing extra memory is not relinquished. This is reproducible with one client and one server, or with many clients.
I'm not sure how to post an example that would demonstrate this, but let me know what else might be useful to know.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version