More > JRiver Media Center 21 for Linux
Memory Leak in AMD64 and RPi builds
mwillems:
--- Quote from: bob on October 20, 2015, 11:19:59 am ---Thanks very much. What are your track change settings?
--- End quote ---
On the Arch PC the track change settings are gapless for sequential album tracks (checked) and otherwise cross-fade aggressive. I should note that I see memory growth on almost every track change whether it happens normally at the end of the track (gapless) or through the skip button (crossfade). I mentioned using skip above as that seemed to speed up the demonstration of the leak, but I did notice that skipping tracks as quickly as possible without waiting for the fade in to finish didn't always result in significant memory growth. The track needs to buffer a bit to trigger it I think.
mwillems:
My settings on all my pi's are gapless for sequential album tracks (checked) and cross-fade aggressive otherwise. I'm currently running along playlist to see if I can reproduce the memory leak on 21.0.14. I definitely can't on 21.0.07
mwillems:
Ok, I can definitely reproduce it in 21.0.14. A single FLAC album (albeit a long one) had my MC memory use jumping a few hundred MB. Stopping one album and starting another seemed to make the biggest jump. I did four albums worth of skipping around, stopping and starting a new album before RAM use got up around 700MB+ and then MC froze and crashed to desktop.
PrinterPrinter:
I don't use gapless but do have 'do not play Silence' ticked. Cross fade aggressive - I hope it helps?
bob:
--- Quote from: mwillems on October 20, 2015, 11:34:26 am ---On the Arch PC the track change settings are gapless for sequential album tracks (checked) and otherwise cross-fade aggressive. I should note that I see memory growth on almost every track change whether it happens normally at the end of the track (gapless) or through the skip button (crossfade). I mentioned using skip above as that seemed to speed up the demonstration of the leak, but I did notice that skipping tracks as quickly as possible without waiting for the fade in to finish didn't always result in significant memory growth. The track needs to buffer a bit to trigger it I think.
--- End quote ---
I set my Wheezy i386 build machine to cross fade aggressive .5 sec and all of the seek, pause, stop to normal (fade-out) and I can't reproduce it.
On the AMD64 Jessie build machine though the same settings are obviously causing a leak.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version