DP9.5 Crashes on Startup - Tried Everything!

[jroo2790]

I've got DP9 running smoothly on a Late 2011 iMac (Yosemite 10.10.5). I've been trying to install it on my Late 2013 Macbook (also Yosemite 10.10.5) and have not been able to open or create any sessions – crashes occur as soon as I select "Open" or "Create Empty" on the startup screen.

I've been in touch with MOTU support, and they seem to be stumped as well. Here's what I've tried:

- Trashing preferences
- Reinstalling (both from the original disk and from a download provided by MOTU support)
- Installing using the program files on iMac (where DP9 is running without issue)
- Repairing disks
- Opening with plugins in safe mode
- Opening with plugins disabled
- Opening from a new user account (with admin privileges)
- Removing all plug-ins
- Checking to make sure all fonts are enabled in Font Book
- Disabling the Welcome Screen in DP9 Preferences (same crash when I go to File>New)
- Uninstalling Soundflower
- Setting Audio I/O to Built-in


When I open DP9, the welcome screen pops up every time. The DP9 logo in the top right disappears after a second as does the Template option (which changes to "Empty"). I do not have any MIDI devices or other external hardware connected.

Any ideas for how to get this running would be greatly appreciated!

[CharlzS]

I vaguely remember that changing the color profile in Display Preferences might fix some odd problems.

[jroo2790]

Thanks for the suggestion! I've tried changing the color profile and have used ColorSync Utility to repair any issues. DP is still crashing

[jroo2790]

Update on opening pre-existing files:

I can open sessions I created on my iMac, but I can't create a new session or save as from there (same crash).

I also tried opening a MIDI file (control+click in Finder and select Open with DP). It also opened fine, but when I tried doing a Save As to save it as a DP session, the application crashes.

[MIDI Life Crisis]

Shot in the dark here: go into Fontbook and validate fonts and remove duplicates. Probably not the solution but worth the effort. IMO.

[cuttime]

I just hate stories like this. In my experience, the tried and true troubleshooting tips almost never work. I have a hunch that you need to look at hardware. There's also scouring the entrails in console for clues. I'd start by running a deep RAM test. There's the Apple hardware test, and as far as I know, this one still works, too:

http://www.kelleycomputing.net/rember/

[cuttime]

And there's this:

viewtopic.php?f=26&t=61817&p=525913&hil ... ts#p525913

[mikehalloran]

RAM is a possibility but more likely an issue if the crash occurs during BTD.

Console.app or the processing monitor should reveal the problem. Something’s trying to load that shouldn’t or can’t load that should unless...

What directory have you selected for new documents? If you ported from another Mac, it may be trying to write to one that doesn’t exist.

You did install in the default location and reboot after installing, yes? Do a Safe Boot then boot normally in case there’s a corrupt path — this rebuilds them and restores caches to default.

[jroo2790]

OMG

I can't believe I got it to work (with a couple work-arounds)....

The script to disable DP9 Crash Reporter WORKED. I have it copied to my applications folder. The only thing not working is when I try to right click a MIDI file and tell it to open using DP9. HOWEVER, I can open it directly from DP9 using File>Open.

Thank you for ending this headache! I thought I was going to have to do a total reset on my Macbook.

[jroo2790]

And to follow-up re: RAM. I did download Rember and run a test, but everything came back good. So, guess is was just the DP9 Crash Reporter?

[HCMarkus]

Cuttime Saves the Day...Film at 11.

[cuttime]

OMG

I can't believe I got it to work (with a couple work-arounds)....

The script to disable DP9 Crash Reporter WORKED. I have it copied to my applications folder. The only thing not working is when I try to right click a MIDI file and tell it to open using DP9. HOWEVER, I can open it directly from DP9 using File>Open.

Thank you for ending this headache! I thought I was going to have to do a total reset on my Macbook.

The disable Crash Reporter script should only be a diagnostic tool. That it should solve the problem in and of itself is rather unlikely, but I won't argue with success. Is there something else going on that would block the Crash Reporter, like an odd firewall setting, or LittleSnitch?

[jroo2790]

No firewall settings or programs I can think of...This Macbook has really only been running Adobe Products/Sibelius/Microsoft Office in the years I've owned it. Just verified that Firewall is off in System Prefs.

[cuttime]

Is there a DP Crash log in Console?

[cuttime]

Cuttime Saves the Day...Film at 11.

And if you stay tuned, we'll find out if an elephant and a five week old kitten really can be best friends forever!