Pro Tools 8 m-powered quits unexpectedly

[akadeem]

I am running Pro tool m-powered 8.0.1cs2 on my macbook
version 10.5.8 , 2.13 processor speed, 2GB of memory, Intel core 2 Duo

well pro tools was working fine not to long ago, but now every time i try to open it. The icon will bounce the avid logo screen appears then pro tools
quits unexpectedly. I then have the option to relaunch, report to apple or ignore. I uninstalled pro tools twice, clean and safe. I re-installed pro tools, updated it and updated my plug-ins. I then tried removing plug-ins, but to no prevail pro tools responded in the same way by quitting unexpectedly.
I then ran disk utility and ran a repair. That did not work either.

The only thing I can think that I did wrong was I ran a series of software updates that were suggested by my software updater. I am all out of ideas so if any one could help that would be greatly appreciated.

[DigiTechSupt]

I don't see that you've trashed preferences yet, or tested from a new admin account.

Can you try those and let us know if anything changes?

Another thing to try - remove all plug-ins from the plug-ins folder, trash prefs, restart and try to relaunch. If that works, we'll know it's a plug-in issue...

[akadeem]

Thank you for your reply, I tried what you recommended but that did not work (.com.digidesign.protoolsLE.plist) was the only file I found in the preference folder. I removed the plug-ins and restarted. but no luck.

[bradch00]

Did you update to 10.5.8 through the software updater or did you download and install the combo update to 10.5.8?

I believe for Leopard and 8.01x the combo update is the recommended approach.

[akadeem]

yes i updated through the software updater

[bradch00]

So I would suggest perhaps downloading and installing the combo update...

[akadeem]

I will try that, thanxs

[akadeem]

That did not work either bradch00. any other suggestions?

[bradch00]

That did not work either bradch00. any other suggestions?
Is there an application dump associated with the message? If so does it indicate which thread number is crashing?

[akadeem]

I'm sorry but I am not sure if I understand what you mean by
"application dump"

[bradch00]

Hi, when you select "report" you should see some details of the state of the program when it abnormally terminated like which "thread" crashed and a number associated with it.

Try to locate that thread number and the module associated with it in the details, it may shine a light on what component is giving you grief.

[DigiTechSupt]

Thank you for your reply, I tried what you recommended but that did not work (.com.digidesign.protoolsLE.plist) was the only file I found in the preference folder. I removed the plug-ins and restarted. but no luck.

Did you test from a new admin account?

[akadeem]

I believe this is what you were referring to:

Thread 0 Crashed:
0 com.apple.CoreFoundation 0x97e4ae94 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 4
1 libobjc.A.dylib 0x96382e3b objc_exception_throw + 40
2 com.apple.CoreFoundation 0x97e521ea -[NSObject doesNotRecognizeSelector:] + 186
3 com.apple.CoreFoundation 0x97e507ec ___forwarding___ + 892
4 com.apple.CoreFoundation 0x97e508b2 _CF_forwarding_prep_0 + 50
5 com.apple.CoreFoundation 0x97d97f39 CFDataGetBytes + 217
6 com.apple.chud.core 0x4b00f0e5 utilGetCFProperty + 193
7 com.apple.chud.core 0x4b00f545 utilGetMemCtrlInfo + 575
8 com.apple.chud.core 0x4b01881e chudInitialize + 935
9 ...gidesign.framework.ProTools 0x0293ae4d



let me know if this helps... and yes I have tried under different admin. account. Thank you guys for all your help. This is driving me crazy!

[akadeem]

this was the rest:

TTimelineSelectionLayer_ForwardDeclarationHack::Re moveReference(TTimelineSelectionLayer*) + 67777
10 ...gidesign.framework.ProTools 0x0293ad20 TTimelineSelectionLayer_ForwardDeclarationHack::Re moveReference(TTimelineSelectionLayer*) + 67476
11 ...gidesign.framework.ProTools 0x028e8ad6 LaunchProTools + 1124
12 com.digidesign.ProToolsMP 0x00007e7a 0x1000 + 28282
13 com.digidesign.ProToolsMP 0x000026c2 0x1000 + 5826
14 com.digidesign.ProToolsMP 0x000025e9 0x1000 + 5609

[DigiTechSupt]

It looks like you have CHUD tools installed. Uninstall them and I bet your problem goes away.

[akadeem]

really? okay so would these CHUD tools have a uninstall application or would I have to simply delete these CHUD tools? and would you have any idea where they might be located?

thanks again

[akadeem]

okay I removed the CHUD, but left my interlock at a friends house will see if that worked later this evening. Thanks again for all your help.

[akadeem]

It worked!! pro tools is working fine now.

[Atang]

I am having the same problem only none of the CHUD tools are existent, and my error report goes on for many more, about 61 total
Thread 0 Crashed:
0 libSystem.B.dylib 0x90f17e42 __kill + 10
1 libSystem.B.dylib 0x90f8a23a raise + 26
2 libSystem.B.dylib 0x90f96679 abort + 73
3 libstdc++.6.dylib 0x9004b005 0x90003000 + 294917
4 libstdc++.6.dylib 0x9004910c __gxx_personality_v0 + 1108
5 libstdc++.6.dylib 0x9004914b std::terminate() + 29
6 libstdc++.6.dylib 0x90049261 __cxa_throw + 101
7 ...gn.framework.CoreFoundation 0x00559883 Sys_MachExceptionHandler::Init() + 1951
8 libSystem.B.dylib 0x90eb1b60 pthread_mutex_lock + 20
9 com.digidesign.framework.DAE 0x03f3e83a FicHostPlugInRunnerInit + 32937
10 com.digidesign.framework.DAE 0x03f40542 FicHostPlugInRunnerInit + 40369
11 com.digidesign.framework.DAE 0x03f3f956 FicHostPlugInRunnerInit + 37317
12 com.digidesign.framework.DAE 0x03f401ca FicHostPlugInRunnerInit + 39481
13 com.digidesign.framework.DAE 0x03f40263 FicHostPlugInRunnerInit + 39634
14 com.digidesign.framework.DAE 0x03f40d15 FicHostPlugInRunnerInit + 42372
15 com.digidesign.framework.DAE 0x03f4a4f7 FicHostPlugInRunnerInit + 81254
16 com.digidesign.framework.DAE 0x03f4a95f FicHostPlugInRunnerInit + 82382
17 com.digidesign.framework.DAE 0x03e05cc4 FicUnRegisterDirectMIDIClient + 41392
18 com.digidesign.framework.DAE 0x03f4ad96 FicHostPlugInRunnerInit + 83461
19 com.digidesign.framework.DAE 0x03e01cdf FicUnRegisterDirectMIDIClient + 25035
20 com.digidesign.framework.DAE 0x03e0f346 FicUnRegisterDirectMIDIClient + 79922
21 com.digidesign.framework.DAE 0x03e017a0 FicUnRegisterDirectMIDIClient + 23692
22 com.digidesign.framework.DAE 0x03e0f00d FicUnRegisterDirectMIDIClient + 79097
23 com.digidesign.framework.DAE 0x03ef4bf2 FicGetSyncPeripheral + 12772
24 com.digidesign.framework.DAE 0x03e14b08 FicGetApplicationInterface + 4776
25 com.digidesign.framework.DAE 0x03ee3349 FicSetFileLoc + 64
26 ...gidesign.framework.ProTools 0x01d7cdcf 0x1bbc000 + 1838543
27 ...gidesign.framework.ProTools 0x01d778e4 0x1bbc000 + 1816804
28 ...gidesign.framework.ProTools 0x01d7d60d 0x1bbc000 + 1840653
29 ...gidesign.framework.ProTools 0x01d7f1b9 0x1bbc000 + 1847737
30 ...gidesign.framework.ProTools 0x01eff81a 0x1bbc000 + 3422234
31 ...gidesign.framework.ProTools 0x01ee8307 0x1bbc000 + 3326727
32 ...gidesign.framework.ProTools 0x01f76d89 0x1bbc000 + 3911049
33 ...gidesign.framework.ProTools 0x01f773cd 0x1bbc000 + 3912653
34 ...gidesign.framework.ProTools 0x023667cc 0x1bbc000 + 8038348
35 com.digidesign.framework.DFW 0x009b1593 TFileHandler::DoRead(bool) + 39
36 com.digidesign.framework.DFW 0x009b15e8 TFileHandler::ReadFile(bool) + 36
37 com.digidesign.framework.DFW 0x009b28b1 TFileBasedDocument::ReadDocument(bool) + 101
38 ...gidesign.framework.ProTools 0x02365aeb 0x1bbc000 + 8035051
39 ...gidesign.framework.ProTools 0x02310171 0x1bbc000 + 7684465
40 com.digidesign.framework.DFW 0x009cd827 TODocCommand::DoIt() + 59
41 com.digidesign.framework.DFW 0x009a5e10 TCommandHandler::PerformCommand(TCommand*) + 86
42 com.digidesign.framework.DFW 0x009a63a9 TCommand::Process() + 31
43 com.digidesign.framework.DFW 0x0099e870 TApplication::ProcessEvent(TEvent*) + 26
44 com.digidesign.framework.DFW 0x0099ead8 TApplication::WakeUp() + 64
45 com.digidesign.framework.DFW 0x00aa5d4c TApplication::GetApplicationVersionComponents(Cmn_ PolyVector<long, false>*) + 3408
46 com.apple.HIToolbox 0x92c5313d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
47 com.apple.HIToolbox 0x92c5257b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
48 com.apple.HIToolbox 0x92c523e0 SendEventToEventTargetWithOptions + 58
49 com.apple.HIToolbox 0x92c80d54 ToolboxEventDispatcherHandler(OpaqueEventHandlerCa llRef*, OpaqueEventRef*, void*) + 356
50 com.apple.HIToolbox 0x92c534f6 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2134
51 com.apple.HIToolbox 0x92c5257b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
52 com.apple.HIToolbox 0x92c6eecc SendEventToEventTarget + 52
53 com.apple.HIToolbox 0x92cdba6c ToolboxEventDispatcher + 86
54 com.apple.HIToolbox 0x92cd82c2 RunApplicationEventLoop + 222
55 com.digidesign.framework.DFW 0x00aac317 DFW_EventLoop::RunApplicationEventLoop() + 11
56 com.digidesign.framework.DFW 0x0099e487 TApplication::Run() + 45
57 ...gidesign.framework.ProTools 0x027fe54c LaunchProTools + 1560
58 com.digidesign.ProToolsMP 0x0000a291 0x1000 + 37521
59 com.digidesign.ProToolsMP 0x0000ab20 0x1000 + 39712
60 com.digidesign.ProToolsMP 0x00004f3f 0x1000 + 16191
61 com.digidesign.ProToolsMP 0x00004e6d 0x1000 + 15981

[Atang]

This also only happens when Im attempting to open a PTF, i can create a new session just fine, im running PT 8.0.3 M powered, with an m audio firewire solo
Macbook 10.5.8, 2.4 GHz intel core 2 duo