More > JRiver Media Center 19 for Mac

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

<< < (3/4) > >>

JohnT:
OK, I was able to reproduce the exact same problem once - can't do it again.

I had Media Network running, playing a track through a USB DAC, then selected "Sleep" from the Apple menu.  Brought it out of sleep, did Cmd-Q, and it beach-balled.  I force quit.  Then when restarting it said the library would be opened in read-only mode and playback was flaky.  I had the same dead [Media Center] entry in the process list as MrC posted above.  Had to reboot to make it work again.  Since rebooting I've tried the same process about a dozen times and can't get it to happen again.

MrC:
Maybe there's a difference with Sleep vs. Deep Sleep?

JohnT:
Possibly, although although it seems like it would have been at the same sleep level each time since I didn't change peripherals or running software or time elapsed in sleep.

bplexico:
Hmmm, if you are running Mavericks, perhaps enabling "Prevent App Nap" for MC might resolve the problem? I have my Mac Mini set to never sleep as I run it headless and use it soley for music, so I have not seen this issue though I do have Media Network enabled.

I realize while that may alleviate the issue, it won't get to the root cause of the beach ball.

p.s. I don't have "Prevent App Nap" enabled.

johnjen:
Just to throw my 2¢ in on this.

It seems to be something that takes a while to instigate.
IOW several albums worth of music with stopping, pausing and un-pausing, restarting, track skipping, etc., seem to be needed to trip this 'beachball freeze on quitting' problem.

I don't know if its these operations (stopping, restarting etc.) or something related, but 'flexing' the programs muscles (fussing with various operational controls) seems to 'help' trigger these sorts of behaviors.

JJ

Navigation

[0] Message Index

[#] Next page

[*] Previous page