More > JRiver Media Center 26 for Linux
JRiver on Raspberry Pi has a memory leak?
mwillems:
--- Quote from: Hendrik on February 10, 2020, 04:04:14 am ---That seems rather unrealistic. Memory allocation is a software thing.
What puzzles me the most is how this wants to be a Linux-exclusive problem. I've run all sorts of memory debuggers (leak finder, heap profiler, the works) and found no suspect results at all.
An actual leak would show up immediately. And even if it somehow stores memory references somewhere that are only free'ed on exit, those would've shown in the heap profiler.
--- End quote ---
Fair enough, just spitballing :)
--- Quote from: bob on February 10, 2020, 08:44:06 am ---Perhaps it a system library mismatch issue?
I'll make another test build on buster and we'll see if the issue goes away for you.
--- End quote ---
If that could cause the issue, then that's a definite possibility as everything I'm running is on either Buster or Arch (which is newer yet).
bob:
--- Quote from: mwillems on February 10, 2020, 09:21:05 am ---Fair enough, just spitballing :)
If that could cause the issue, then that's a definite possibility as everything I'm running is on either Buster or Arch (which is newer yet).
--- End quote ---
You have a PM
mwillems:
Ok I tested with the latest build and it did not resolve the memory leak. I tested on both debian buster and on Arch clients, they behaved similarly. Some things I noticed: the memory increase typically occurs alongside mediacenter pegging one CPU core for somewhere between five and ten seconds. It also seems to coincide with SSDP broadcasts, but that's harder to say as those occure pretty frequently anyway. For a test, I tried disabling all non-jriver SSDP devices on the network, but that didn't change anything.
I'm stumped!
bob:
--- Quote from: mwillems on February 10, 2020, 01:00:39 pm ---Ok I tested with the latest build and it did not resolve the memory leak. I tested on both debian buster and on Arch clients, they behaved similarly. Some things I noticed: the memory increase typically occurs alongside mediacenter pegging one CPU core for somewhere between five and ten seconds. It also seems to coincide with SSDP broadcasts, but that's harder to say as those occure pretty frequently anyway. For a test, I tried disabling all non-jriver SSDP devices on the network, but that didn't change anything.
I'm stumped!
--- End quote ---
Still though, it goes away if syncing is off, correct?
mwillems:
--- Quote from: bob on February 10, 2020, 01:11:46 pm ---Still though, it goes away if syncing is off, correct?
--- End quote ---
Yes, the memory stops increasing when the "auto-sync with server" client setting is off. It doesn't release any memory that's already grown.
But yeah, it's easy enough to live with that setting off, I just wanted to crack the case!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version