More > JRiver Media Center 26 for Linux
JRiver on Raspberry Pi has a memory leak?
mwillems:
--- Quote from: Hendrik on February 08, 2020, 12:00:02 pm ---I'm not seeing any growth in the data. It pretty fast comes up to around 600mb and then stays there pretty consistently - a similar result to what I'm seeing here locally.
--- End quote ---
The reported memory looked like it grew slightly on my end, but I know what you mean. I tried it again without valgrind and it grew plenty fast, so it seems like something about the valgrind environment is changing the behavior. Not sure what that might be though.
Is it possible to run valgrind multi-threaded? It seems to peg one core for thirty seconds or a minute or so every minute or so and the interface and music playback stutter badly until it finishes whatever it's doing (presumably making a checkpoint?), and then runs normally again for a while thirty seconds or so. I wonder if some of the network activity is just timing out and not completing, maybe? If there's an easy way to run it across multiple cores that might let it act more normally.
mwillems:
So the inability to reproduce the leak in valgrind got me thinking: valgrind is kind of a software virtual machine that executes the code in a processor-neutral virtual CPU, right? So it made me wonder if CPU architecture might have something to do with it. Most of my home build out was done circa 2013-2015, so most of my hardware is haswell or bay trail hardware (e.g. I can repro the memory leak on an i7-4790K, an i5-4250U, and an Atom Z3735F). I don't have much newer hardware floating around, but I wonder if that might be a clue?
Hendrik:
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.
JimH:
A driver? Or a plug-in?
bob:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version