More > JRiver Media Center 24 for Linux
JRiver Media Center 24.0.32-4 BETA for Debian Jessie (amd64, i386 and arm)
bob:
--- Quote from: mwillems link=topic=116196.msg803673#msg803673 date=1528412644
[i ---Also, do you see a registration check in the log for each refresh?[/i]
Yes, I do
--- End quote ---
I checked in there and it seems good but can you try without sync turned on and see if it still does the registration checks please?
mwillems:
--- Quote from: bob on June 08, 2018, 10:30:55 am ---I checked in there and it seems good but can you try without sync turned on and see if it still does the registration checks please?
--- End quote ---
Ok, I still see the registration checks without auto-sync on, but strangely, I also see some memory growth with auto-sync disabled but only when clicking refresh. I previously hadn't seen any memory growth with auto-sync disabled, and I still don't see any passive memory growth with auto-sync disabled. Refresh seems to cause memory growth regardless of the auto-sync setting.
So to summarize what I'm seeing on multiple clients:
With auto-sync with server enabled: Gradual increase in memory used just leaving Mediacenter open. Playback leads to faster memory increases.
With auto-sync with server disabled: Increase in memory used on clicking refresh, no passive memory leak with mediacenter sitting idle.
bob:
So far what I'm seeing:
In the log, minimal use of the registration helper, 8 invocations total.
During playback of 20k very short files as a media server client with memory playback off:
No increase in the number of file handles and sockets used.
Refreshing with sync on does no network activity with the MC server.
Running gapless track transitions, I see only a few calls to the ALSA driver setup code in the log.
Under top it DOES seem to slowly increase memory usage with each track played. I plan on trying the null device which should bypass the ALSA code in a while...
Edit: The null device does the same thing so it's not ALSA.
Edit2: but if I turn off sync I have no memory growth.
mwillems:
--- Quote from: bob on June 08, 2018, 11:55:19 am ---So far what I'm seeing:
In the log, minimal use of the registration helper, 8 invocations total.
During playback of 20k very short files as a media server client with memory playback off:
No increase in the number of file handles and sockets used.
Refreshing with sync on does no network activity with the MC server.
Running gapless track transitions, I see only a few calls to the ALSA driver setup code in the log.
Under top it DOES seem to slowly increase memory usage with each track played. I plan on trying the null device which should bypass the ALSA code in a while...
Edit: The null device does the same thing so it's not ALSA.
Edit2: but if I turn off sync I have no memory growth.
--- End quote ---
That sounds a lot like what I'm seeing, so you've mostly reproduced it, which is exciting! Thanks for hanging with this.
Navigation
[0] Message Index
[*] Previous page
Go to full version