More > JRiver Media Center 23 for Linux
Suspected Memory Leak in Linux Builds
craigmcg:
I'm not using Last FM.
mwillems:
--- Quote from: bob on April 09, 2018, 09:35:31 am ---Are any of you using Last.FM updating?
--- End quote ---
I'm not using last.fm either.
mwillems:
--- Quote from: mattkhan on April 09, 2018, 09:35:03 am ---FWIW I have 2 separate linux machines connected to a windows server, I do have that option checked and I don't see any evidence of a socket leak
--- End quote ---
Do either of your clients have media network enabled? Or are they just connected as clients to the library server? Just trying to think of other config differences that might be relevant. In my case media network is enabled on all computers, but DLNA controller and server are disabled on the clients.
mattkhan:
--- Quote from: mwillems on April 09, 2018, 07:46:24 pm --- In my case media network is enabled on all computers, but DLNA controller and server are disabled on the clients.
--- End quote ---
I have the same setup though my Linux boxes run Debian Buster
bob:
--- Quote from: craigmcg on April 09, 2018, 09:17:34 am ---Quote from Bob
"Interesting. I wonder if it's an issue in the Mac and Windows builds as well."
I can't say that it is for sure but when I turned off Auto synch on the client PCs (all running Win 10 x64), the library server on the server PC stopped the crashing that has been bugging me for months (first thought that it was network switch related then Win 10 networking changes, etc.). While I only made the change yesterday I haven't had the crash on the server PC since (was happening a few times each day). I have 5-6 client PCs connecting to the server using the Library server.
Thanks to Bob and mwillems for pointing me to what seems to be the solution.
--- End quote ---
Is your system all windows (the server PC is windows 10 as well)?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version