More > JRiver Media Center 32 for Mac

Upgrade crash - server mode lockup

<< < (4/4)

bob:
This sure sound like a deadlock in the main thread.
Matt made a change to not stall on a MCWS call when the db is being changed in MC32 but I don't see that would cause this, if anything it would alleviate it.
Perhaps turn on logging on the side that freezes and zip that up and send it to me
bob (at) jriver (dot) com.
It should be possible to see what the last thing running on the main thread was.

TP1964:
ok - on my side, I opened MC, enabled logging - and then closed MC and left the MC Server running - as I’ve said previously, it takes days for this to show up, so I’ll zip up the log and send it to you as soon as it does it. Thanks, Bob. —T

crashjtm:
Bob,
I had logging enabled when it hung.  The log file starts at 12:30pm and the hang occurred around 1:20pm.

My setup - the machine I normally use is my Mac Mini M2.  I always have the server running so I can access my music whenever I want to.  At the time this happened, I was at the desktop running locally.  No other clients in should have been accessing the system until after the freeze.  (After the freeze, I started testing via Postman and JRemote.)

Logs will be on the way in a moment.

Joe

crashjtm:
Out of curiosity, I turned off my firewall and started doing a packet capture which I reset every so often.  I ran all weekend with no issues so that's not going to help as a diagnostic tool though I will keep running it in case something happens.

I've never run a packet capture at home before.  My media server is getting requests from expected devices like my Blu-Ray player and TVs which are DLNA clients but it is also getting hit by light bulbs and smart outlets.  My home network is a noisy place.

Navigation

[0] Message Index

[*] Previous page