10.12.6 fixed crashes? (It didn't)

[philbrown]

Wasn't sure which sub-forum this belonged in.

I'll leave out 95% of my horror story of the last couple of months, but for the FIRST TIME this morning after just installing 10.12.6 I quit DP and did NOT get a COQ. I have 'guarded optimism' that maybe this has fixed something but it's too early to tell. Fingers crossed and... should I throw salt over my shoulder or something? Need to google that voodoo good-luck stuff and at least avoid ladders and mirrors I guess.

[MIDI Life Crisis]

COQ=crash on quit

COQ10=good for your heart

[RodneySauer]

Wasn't sure which sub-forum this belonged in.

I'll leave out 95% of my horror story of the last couple of months, but for the FIRST TIME this morning after just installing 10.12.6 I quit DP and did NOT get a COQ. I have 'guarded optimism' that maybe this has fixed something but it's too early to tell. Fingers crossed and... should I throw salt over my shoulder or something? Need to google that voodoo good-luck stuff and at least avoid ladders and mirrors I guess.

I have not been getting crash on quit from Digital Performer at all, but just trying to upgrade to 10.12.6 made my computer unable to shut down properly. And since it can't shut down properly, I need to force restart it, and with a force restart, it won't upgrade, so I'm still at 10.12.5.

[mikehalloran]

Wasn't sure which sub-forum this belonged in.

I'll leave out 95% of my horror story of the last couple of months, but for the FIRST TIME this morning after just installing 10.12.6 I quit DP and did NOT get a COQ. I have 'guarded optimism' that maybe this has fixed something but it's too early to tell. Fingers crossed and... should I throw salt over my shoulder or something? Need to google that voodoo good-luck stuff and at least avoid ladders and mirrors I guess.

I have not been getting crash on quit from Digital Performer at all, but just trying to upgrade to 10.12.6 made my computer unable to shut down properly. And since it can't shut down properly, I need to force restart it, and with a force restart, it won't upgrade, so I'm still at 10.12.5.

Boot into the Repair Partion (Option r) and reinstall the OS. This downloads and installs 10.12.6 without updating 10.12.5. If for any reason, it can't, run Repair Disk from Disk Utility first while booted into Repair.

If you do not have a Repair Partition because your boot drive was created by a clone, download the complete installer from the App Store and run it—this does the same thing and installs a Repair Partition.

If your system is so corrupted that none of these work, post that and I'll post how to create an emergency Boot and repair installer using an 8G or larger USB thumb drive or SDHC card.

It's probable that just booting into Repair and running Disk Utility will let the upgrade function normally. Run Repair Disk on the whole drive and the partition — often one doesn't work till the other has been done and I can never predict which it will be.

[philbrown]

I spoke too soon on the crash fix. Back to consistent crash on quit.

[RodneySauer]

Thanks, Mike: that technique (command-R restart, Disk First Aid, reinstall system) was partially successful: I now have system 10.12.6. However, the computer still can't shut down properly. I've looked elsewhere and tried a few things (removing Startup items, unplugging all peripherals), but nothing seems to work. However, that's clearly not a Digital Performer problem, so I'm not sure this is the right forum for it.

[mikehalloran]

Console.app is your friend unless you are generating crash reports and then they are.

viewtopic.php?f=4&t=63683

Back when I was in OS 10.8.2 Hell, MOTU and Apple support were quite helpful in letting me know what files and .kexts were causing problems. Finding and removing wasn't that hard once I knew what to look for. I still had to learn how to find system and hidden files.

[RodneySauer]

Finally took it to the Apple Store: they had to do a complete disk erase and reinstall from their servers. Fortunately that took care of it, and the Time Machine backup/restore only took about three hours. Back in business.

[mikehalloran]

Finally took it to the Apple Store: they had to do a complete disk erase and reinstall from their servers. Fortunately that took care of it, and the Time Machine backup/restore only took about three hours. Back in business.

Good. Probably faster than trying to look up everything that would have showed up in Console.app to figure out the thing or things that were causing the problem — been there, done that and it can take a long time.

Migration Assistant is pretty good at ignoring code that isn't part of the Applications and files it's pulling over from Time Machine. Not perfect—nothing is—but it's so much better than the cloning apps that try to restore everything including the old problems.

[Shooshie]

COQ=crash on quit

COQ10=good for your heart

CoQ-10, Good for the heart

10 COQ's Terrible for the heart.

Both — Status quo?

Just don't mess with my blue suede shoes!

[Phil O]

I get crash on quit (in 9.13) under the following conditions:

Open a project created in a version earlier than 9.13.
then...
Quit before making any edits and not saving first.

If I open, save then quit I don't get the crash.



I've just gotten in the habit of command-s, command-q and haven't seen any COQs (or COQ10s for that matter).

Phil


[edit] Someone might say, "Phil why would you open a project and do no edits then quit?" Well, usually it's open a project, listen to it then quit.

[MIDI Life Crisis]

You might want to try loading the chunk into a new project file. Might be the project file is corrupted.

[MIDI Life Crisis]

ps - unless you close the project before quitting- of course.

[philbrown]

I get crash on quit (in 9.13) under the following conditions:

Open a project created in a version earlier than 9.13.
then...
Quit before making any edits and not saving first.

If I open, save then quit I don't get the crash.



I've just gotten in the habit of command-s, command-q and haven't seen any COQs (or COQ10s for that matter).

Phil


[edit] Someone might say, "Phil why would you open a project and do no edits then quit?" Well, usually it's open a project, listen to it then quit.

Thanks for that, Phil. My COQ's are 100% of the time no matter what I do – except a recent mastering project created in 9.13. It's been the same COQ's with 9.13, 9.12 and even tried 9.02 with pre-gen turned off. Starting to suspect what I bolded in your post might be the cause. I've been working on my band's album for just short of a year and all those songs were started in 8.07 as well as my day job editing files which were also created in 8.07. The album is at Discmakers as we "speak", so my next step is to build a fresh file for my regular editing work, which I can do in 2 or 3 days when my present job is done. I'll post back if that works.

[Phil O]

Thanks, Phil. Please let us know what happens.

The other Phil