PT 11 crashing when closing session

[Christopher Dobrian]

Our system is:
Mac Pro 2 x 2.4 GHz Quad-Core Intel Xeon, 32 GB RAM
Mac OS 10.8.5
D-Command 24-channel control surface
Avid Sync HD, synching two HD I/O interfaces, and one Apogee Symphony I/O for a total of 24 channels of I/O
XMON audio monitor
HDX card upgraded from our original Accel 3 system
JL Cooper Surround Panner
Pro Tools 11.3.2 and Pro Tools 10.3.10

Our problem is:
When closing a session in Pro Tools 11, either Pro Tools crashes immediately or the File menu becomes grayed out so that no other file can be opened. This problem does not occur when using Pro Tools 10.

Things we've tried:
Reinstalled Pro Tools
Deleted /Users/<username>/Library/Preferences/com.avid.ProTools.plist

We'll welcome any suggestions of how to resolve this problem. Thank you.

-- Chris

[Darryl Ramm]

One session? Some sessions or all sessions? If one/few they may be corrupted.

If not that this problem can be caused by plugins, I would dive straight in and remove all plugins from the plugin folder (and trash prefs) and test. That should have been tried before you got to reinstalling Pro Tools. When you trash prefs use se Pro Tools Prefs helper and trash everything, or at least follow the full instructions for trashign prefs.

If that is not it leave all the plugins uninstalled and try testing from a new admin account with new empty sessions.

[Christopher Dobrian]

Thanks for the response, Darryl.

In answer to your question, it happens with ANY session, including new sessions, on ANY account (which leads me to believe that if there's a corrupted file it's probably a systemwide file, not a user file).

Your advice to move all plug-ins to another location and start afresh, to see if that solves the crashing problem, is a good one, of course, and I'll likely try that next. If that works, I'm not looking forward to the tedious process of replacing plug-ins incrementally to find the culprit. But if I must I must.

I was hoping someone had already solved this problem with a straightforward (simpler) fix and could give precise steps to follow.

I do appreciate the thorough advice you gave, though.

(I'm still open to hearing from others!)

--Chris

[Darryl Ramm]

Just do it. It only takes about a minute to at least check if plugins are at fault.... longer to find the plugin(s).


Sent from my iPhone using Tapatalk