More > JRiver Media Center 19 for Mac

Cmd-Q leads to spinning beach ball and system must be rebooted

<< < (2/4) > >>

JohnT:

I guess I was overly optimistic on this one - I thought it would be easy to repro. Not so.

Looks like a frozen process is being left around following the application termination.  I've seen this happen here once or twice in the past, where MC would open the database in read-only mode because of the stuck process.  I couldn't figure out a way to get rid of the process other than rebooting, and wasn't able to reproduce the issue or glean anything from logs, etc.

Need to collect more information.
1. Send a log file after MC gets into a "problematic state".
2. There are different messaging routes for program termination, so see if terminating with the close box or the menu gets rid of the problem. (longshot I know)
3. If you have Media Network enabled and don't always need it, try disabling it and see if the problem goes away.  I'm suspicious that there's something about a network connection left hanging.

MrC:
I do have Media Network enabled, and I have a hunch this was the suspect issue.  In fact, I don't recall seeing this issue *until* I enabled Media Network recently.

I just tried to quit MC using the close button (previously I always used Cmd-Q).  It is not stuck, but I have not yet tried Force Quit.

There is a log in my dropbox folder for you.

JohnT:
Thanks.  The log looks pretty standard, no smoking guns there.

I'll do multiple trials of leaving our Mac Mini playing in network mode for a while and then terminating with Cmd-Q to see if I can repro.

MrC:
I'm running MC under lddb right now, just in case I catch anything.  So far, all Quits have been good, even with Media Network enabled.  I'm wondering if there is a relation with the Mac going to sleep and then waking.

JohnT:
Yes, I'll test the sleep/wake scenario as well.

Navigation

[0] Message Index

[#] Next page

[*] Previous page