10.3.3 crashes on launch

[gtomassetti]

Details are in signature.

Updated to 10.3.3 on Mac Pro with no issues at all. On MacBook Pro, PT will not launch. Tried uninstalling and reinstalling; did a clean uninstall and reinstalled; did a file system check. PT crashes on every launch attempt.

It doesn't appear that I can post attachments, so here's the top part of the crash report. Any input would be appreciated.

Process: Pro Tools [161]
Path: /Applications/Avid/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 10.3.3.111 (10.3.3f111)
Build Info: Unknown-10330111~111
Code Type: X86 (Native)
Parent Process: launchd [108]

Date/Time: 2012-12-23 00:20:55.486 -0500
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 86084 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 5 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: 500CC788-9C81-4CAF-AAFA-5E59875F8916

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x99a6b114 CFRetain + 212
1 com.apple.CoreFoundation 0x99a75962 __CFBasicHashAddValue + 50
2 com.apple.CoreFoundation 0x99a757e7 CFBasicHashAddValue + 167
3 com.apple.CoreFoundation 0x99aa012c CFDictionaryCreate + 108
4 com.digidesign.framework.DFW 0x006d8752 DFW_CocoaUtils::NSStringToString(NSString*) + 322
5 com.digidesign.framework.DFW 0x00662f9d DFW_PainterQuartz::GetCFAttrStrFromString(char const*) + 413
6 com.digidesign.framework.DFW 0x00663164 DFW_PainterQuartz:rawTextBox(Cmn_Rect<long> const&, std::string const&, DFW_Painter::EJustification, bool, bool, bool, bool) + 164
7 com.digidesign.framework.DFW 0x00658c43 TStaticText::ImageText(std::string const&, Cmn_Rect<long> const&, DFW_Painter::EJustification) + 211
8 com.digidesign.framework.DFW 0x00659b2c TStaticText:raw(VRect const&) + 316
9 com.digidesign.framework.DFW 0x00570b98 TView::HandleDraw(VRect const&) + 712
10 com.digidesign.framework.DFW 0x00570b10 TView::HandleDraw(VRect const&) + 576
11 com.digidesign.framework.DFW 0x00570b10 TView::HandleDraw(VRect const&) + 576
12 com.digidesign.framework.DFW 0x00674b25 DFW_PainterOpenGL:rawRect(Cmn_Rect<long> const&) + 37781
13 com.apple.AppKit 0x9320c61e -[NSView _drawRect:clip:] + 3510
14 com.apple.AppKit 0x9320b2bc -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1600
15 com.apple.AppKit 0x932097db -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVis ibleRect:rectIsVisibleRectForView:topView:] + 711
16 com.apple.AppKit 0x9320a7b7 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVis ibleRect:rectIsVisibleRectForView:topView:] + 4771
17 com.apple.AppKit 0x932a89f7 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVis ibleRect:rectIsVisibleRectForView:topView:] + 575
18 com.apple.AppKit 0x93205c96 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVi sibleRectForView:] + 3309
19 com.apple.AppKit 0x9316684b -[NSView displayIfNeeded] + 818
20 com.apple.AppKit 0x9311a60d -[NSNextStepFrame displayIfNeeded] + 98
21 com.apple.AppKit 0x9312fb64 -[NSWindow displayIfNeeded] + 204
22 com.digidesign.framework.DFW 0x0066f5c4 DFW_PainterOpenGL:rawRect(Cmn_Rect<long> const&) + 15924
23 com.digidesign.framework.DFW 0x0066d792 DFW_PainterOpenGL:rawRect(Cmn_Rect<long> const&) + 8194
24 com.digidesign.framework.DFW 0x0055a720 TWindow::Update() + 96
25 com.digidesign.ProTools 0x0000fa5a 0x1000 + 59994
26 com.digidesign.ProTools 0x00010358 0x1000 + 62296
27 com.digidesign.ProTools 0x0000effd 0x1000 + 57341

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x96d1a382 kevent + 10
1 libSystem.B.dylib 0x96d1aa9c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x96d19f59 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x96d19cfe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x96d19781 _pthread_wqthread + 390
5 libSystem.B.dylib 0x96d195c6 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x96d19412 __workq_kernreturn + 10
1 libSystem.B.dylib 0x96d199a8 _pthread_wqthread + 941
2 libSystem.B.dylib 0x96d195c6 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x96cf3b36 semaphore_wait_trap + 10
1 ...idesign.framework.digitrace 0x0144598a digitrace_initialize + 10122
2 ...idesign.framework.digitrace 0x0144a0df DigiTraceIsActiveFunc + 1263
3 ...idesign.framework.digitrace 0x0144a265 DigiTraceIsActiveFunc + 1653
4 ...idesign.framework.digitrace 0x0144a3c1 DigiTraceIsActiveFunc + 2001
5 libSystem.B.dylib 0x96d21259 _pthread_start + 345
6 libSystem.B.dylib 0x96d210de thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x96d19412 __workq_kernreturn + 10
1 libSystem.B.dylib 0x96d199a8 _pthread_wqthread + 941
2 libSystem.B.dylib 0x96d195c6 start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x99a892e7 ebx: 0x99a6b04d ecx: 0x00000000 edx: 0x028284d0
edi: 0x028284d0 esi: 0x00000000 ebp: 0xbfffe308 esp: 0xbfffe2f0
ss: 0x0000001f efl: 0x00000246 eip: 0x99a6b114 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xa054320d

[gives]

[QUOTE=gtomassetti;1991336]Details are in signature.


I started having a crash today ironically when I tried to render commit an elastic time in Xform. Crashed every time. Running 10.7.5 and 10.2.. Thinking up updating to 10.3.3, but not I'm not sure. I NEVER have crashes either. My other i7Macbook Pro has had no problem at all with 10.3.2 and OS 10.8.2. Very strange. I"ll keep an eye on it. G

[gtomassetti]

This is new territory for me, because I've really had very good luck with PT's stability from version 8 onward.

Another possible clue is this: As I'm going through installer, there comes a screen that asks me if I want to install for all users of this computer. I don't believe that this happened during the install on my Mac Pro, and I don't ever recall seeing this before. There are no other accounts on my MBP beside my normal administrator account and the default guest account.

I don't know if this has anything to do with the problem, but I may try setting up a new account and installing 10.3.3 there to see if I can launch.

[gtomassetti]

Curiouser and curiouser…

Did yet another clean uninstall, created a new administrative account, installed 10.3.3 there, and it opened with no issues.

Uninstalled from there, logged off, deleted that account, and logged back into my normal account. This time, the install didn't ask if I wanted to install for all users, but PT still crashed immediately on launch.

One last thing to try: I'll revert back to the previous version by way of CCC, and try to install 10.3.3 over that.

[gtomassetti]

Well, I'm not sure why, but I got it to work.

I reverted to a system backup that was a couple of days old, and 10.3.2 opened with no problems.

Then, rather than uninstalling 10.3.2, I just installed 10.3.3, and it opened immediately.

I wonder what got lost earlier that kept 10.3.3 from opening.

[chrisdee]

Originally Posted by gtomassetti

Then, rather than uninstalling 10.3.2, I just installed 10.3.3, and it opened immediately.

Great. And always good to have backup.

Just wonder when you first uninstalled 10.3.2 did you keep preferences and settings or did you do a complete uninstall ?

[gtomassetti]

Originally Posted by chrisdee

Just wonder when you first uninstalled 10.3.2 did you keep preferences and settings or did you do a complete uninstall ?

My procedure was to do what I always do; a safe uninstall, then an install of 10.3.3. As I mentioned, it worked flawlessly on my Mac Pro, but for whatever reason(s), something or other got messed up on the MBP. Then I tried the clean uninstall, re-downloading the update (at first I had moved the download between computers via a FW drive, something else I've always done), and that didn't work either. That was when I started trying all the other things.

Fortunately, I have not one but 2 CCC bootable drives for this computer (see below). What I did was boot to a hybrid USB drive, made sure 10.3.2 opened correctly, and then used CCC to clone the USB drive back to the MBP drive, which is an SSD. Once I rebooted to the SSD, I made sure again that 10.3.2 opened, then did the update without any uninstalling, and that was what worked.

I'm a little surprised that I thought of doing that, because it was getting on after 0200 EST, and I had to get up to play a couple of Lessons and Carols services just a couple of hours later…

Originally Posted by chrisdee

Great. And always good to have backup.

Yup. For my MBP, in addition to my normal Time Machine USB drive, I have two other USB drives that I back up to with CCC: The original HD, and then the hybrid drive I replaced the original with. They're both in OWC enclosures, and I clone the system drive to them at least every couple of days. So even with all this rigmarole this time around, I didn't lose so much as a single file.

On my Mac, the boot drive is an Accelsior SSD PCIe card, so the original HD in bay 1 is actually now the CCC backup drive.

To say that I'm somewhat obsessive about redundant backups is like saying the Atlantic Ocean is rather damp…

[gives]

Originally Posted by gtomassetti

Well, I'm not sure why, but I got it to work.

I reverted to a system backup that was a couple of days old, and 10.3.2 opened with no problems.

Then, rather than uninstalling 10.3.2, I just installed 10.3.3, and it opened immediately.

I wonder what got lost earlier that kept 10.3.3 from opening.

That was it probably. Always delete the OLD prefs no matter what volumes, Everything if they Uninstaller doesn't. I always check.
They say to always do the Uninstall no mater what. Since this was a FULL installer to begin with on 10.3.3, that is what I believe happened. Clean Uninstall you mean just the Protools uninstall correct? Not he OS. I see you are running OS 10.6.8

[MixerGuy]

Complete uninstall is always best.

Also deleting ALL prefs is key

As is repairing permissions.

And a complete shut down.

All the above before you even launch the new PT install.

[MixerGuy]

Also 10.7.4 is working great here.

Better than 10.8.x from some accounts.