More > JRiver Media Center 21 for Linux
Memory Leak in AMD64 and RPi builds
mwillems:
--- Quote from: bob on November 03, 2015, 02:09:24 pm ---My resident memory use actually went down after a couple of days.
--- End quote ---
I've been intermittently monitoring my work Pi (which doesn't have a network hook up), and I haven't seen any increases in memory usage at all. I haven't seen decreases though, maybe you can share your secret as I need all the free memory I can get ;D
Mark_NL:
Don't know if this is usefull, reporting things you already know and specially considering the unusual setup MC-arm is running on. (OrangePI – Debian Jessie on an ancient kernel)
However, over the weekend set up a Munin node on the OPI and saw, as some reported before, MC-ARM 20.129 is leaking too.
On the enclosed graph the first 2 periods of several hours playing (from server > sent to) are MC-ARM 20.129, the third is MC-Arm 21.14. Memory increase is obviously steeper with 21-14, but still quite considerable with MC20.
At the moment it is running MC21-17-3. EDIT: seems to be the same as 20.0.129
unfortunately i can't attach a monitor so network is essential to oparate.
I wonder if switching off the Media Network and playing from a local disk would do be equivalent to running without anny network connected?
bob:
--- Quote from: Mark_NL on November 04, 2015, 03:41:37 am ---Don't know if this is usefull, reporting things you already know and specially considering the unusual setup MC-arm is running on. (OrangePI – Debian Jessie on an ancient kernel)
However, over the weekend set up a Munin node on the OPI and saw, as some reported before, MC-ARM 20.129 is leaking too.
On the enclosed graph the first 2 periods of several hours playing (from server > sent to) are MC-ARM 20.129, the third is MC-Arm 21.14. Memory increase is obviously steeper with 21-14, but still quite considerable with MC20.
At the moment it is running MC21-17-3. EDIT: seems to be the same as 20.0.129
unfortunately i can't attach a monitor so network is essential to oparate.
I wonder if switching off the Media Network and playing from a local disk would do be equivalent to running without any network connected?
--- End quote ---
It doesn't help to switch off media network, you need to pull the ethernet cable. This points to an issue in the socket listener code I believe.
Mark_NL:
--- Quote from: bob on November 05, 2015, 12:48:15 pm ---It doesn't help to switch off media network, you need to pull the ethernet cable. This points to an issue in the socket listener code I believe.
--- End quote ---
I noticed,
it cuts it almost in half though, maybe I've got two different hiccups.
Mark_NL:
Being in the memory monitoring anyway, fired up a sleeping Debian Jessie VM with MC21 Amd64.
(there is no audio device, output > NULL)
Suspecting something with cover-art to contribute to growing footprint of MC-Arm, I did the same experiment on de Amd64 :
Play tracks with relatively big cover art included in the file (no thumbs build) random from a local library:
a) standard-view location “audio” with “display” in left bottom open (player is current playback zone)
b) (on start up) mini-view and start playing current playlist
a: severe memory growth ; b: modest memory growth
And I have seen modest memory growth on my “main” mediaserver (MC-32bit on 64 bit Arch Linux) if I accidently let the view in state “a” with the render it serves as current playback zone.
Navigation
[0] Message Index
[*] Previous page
Go to full version