More > JRiver Media Center 24 for Linux
JRiver Media Center 24.0.28 for Debian Jessie (amd64, i386 and arm)
bob:
--- Quote from: Mike Noe on May 17, 2018, 02:09:53 pm ---Huge mem leak of some kind:
--- Code: ---The process mediacenter24 (with pid 1966) is using approximately 2.4 GB of memory.
It is using 2.4 GB privately, and a further 12.7 MB that is, or could be, shared with other programs.
Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 2.9 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 2.4 GB.
--- End code ---
Did not see this in 26. Basically, just start MC, start playing a list and then about 30 minutes later, the above. No JRWorkers running.
--- End quote ---
What kind of material are you playing?
What's the output device?
Also, what are your audio settings for track transitions? (gapped, gapless, and the rest).
What command are you using to provide the message about memory usage?
Mike Noe:
1. Playing APEs and FLACs
2. Alsa (Pulse Audio Sound Server)
3. X-fade aggressive (4s), Do not play silence/Use gapless for seq album tracks
4. Using Plasma5's KSysguard system monitor (I did not try top)
I notice also a not-insignficant I/O rate as well, GBs of data over a few hour period...weird
mwillems:
--- Quote from: Mike Noe on May 17, 2018, 05:44:32 pm ---1. Playing APEs and FLACs
2. Alsa (Pulse Audio Sound Server)
3. X-fade aggressive (4s), Do not play silence/Use gapless for seq album tracks
4. Using Plasma5's KSysguard system monitor (I did not try top)
I notice also a not-insignficant I/O rate as well, GBs of data over a few hour period...weird
--- End quote ---
Is this local playback or is there a client-server setup involved; I've still got a pretty big memory leak on linux clients when "auto-sync with server" is enabled.
Mike Noe:
Technically local playback, but I do have 5 zones, so technically it's not just the Alsa device. 1 zone uses a USB-DAC, another zone uses the HDMI device, another zone uses the mobo HD audio device.
In addition, I have a separate process that runs for each zone on my LAN (there's also an MC server on a laptop) that exposes an MPRIS interface for that zone, which I then can access via my android device with KDE Connect.
Then, there is a plasmoid running that polls each zone for playback status (QML/JS type thing) every few seconds. So there is more than a little activity against the MCWS.
BUt, I've had this going for quite some time (way back to early 23.x) and this huge memory alloc just started happening with 24.28.
bob:
--- Quote from: Mike Noe on May 17, 2018, 08:15:11 pm ---Technically local playback, but I do have 5 zones, so technically it's not just the Alsa device. 1 zone uses a USB-DAC, another zone uses the HDMI device, another zone uses the mobo HD audio device.
In addition, I have a separate process that runs for each zone on my LAN (there's also an MC server on a laptop) that exposes an MPRIS interface for that zone, which I then can access via my android device with KDE Connect.
Then, there is a plasmoid running that polls each zone for playback status (QML/JS type thing) every few seconds. So there is more than a little activity against the MCWS.
BUt, I've had this going for quite some time (way back to early 23.x) and this huge memory alloc just started happening with 24.28.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version