More > JRiver Media Center 26 for Linux
JRiver on Raspberry Pi has a memory leak?
mwillems:
--- Quote from: bob on February 07, 2020, 09:15:46 am ---Ok, thanks. It sure seems like you've narrowed it to the sync but I can't see what. Are you set to download lyrics on playback? Those would get synced back too.
--- End quote ---
I thought that might be it and disabled it, but it made no difference sadly
--- Quote ---I'm starting to wonder if there is something specifically with your client machine going on. What is your output device?
--- End quote ---
So I can reproduce this (on prior builds) on three different amd64 linux client machines (one debian, two arch), and they all use different output devices, so I think it's more likely something specific to my network environment. But in the interest of troubleshooting: one is outputting to a PCI device (an old asus ST with daughter board), one is outputting to a USB DAC (an ODAC), and the other is outputting to an internal laptop soundcard (integrated in the mobo).
--- Quote ---Can you zip up your settings files (for the client) and email them to me bob (at) jriver (dot) com ?
--- End quote ---
You mean a library backup? I'll send one from one of the clients shortly.
Hendrik:
I've sent you a PM with a special version and some instructions, if you're able and willing. :)
mwillems:
So, I'm testing now, but it's very slow-going. Valgrind slows playback to a crawl so a five-minute song might take ten or twenty minutes to play. I'll let it run for a few hours and report back.
In terms of methodology, I ran the debug build without valgrind first as a control. I played one album and added another to the queue and let it run for four or five songs. I saw memory growth with the debug build to about 1G and rising. Now I'm running with valgrind using the exact same albums, etc., so hopefully we can capture something.
mwillems:
Ok I ran it with valgrind per your instructions for a good while. The output is gzipped and attached (there didn't appear to be anything private/personally identifiable in the output). One note is that the memory usage appeared to grow much, much more slowly while running under valgrind (after twelve songs or so the memory never got close to 1GB, that I saw), but the memory usage did appear to be slowly rising even so. Hopefully this helps, and let me know if I can help with anything else!
Hendrik:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version