|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Help with this crash report!!
Can someone can explain why my pro tools crashes?
Process: Pro Tools HD [960] Path: /Applications/Digidesign/Pro Tools/Pro Tools HD.app/Contents/MacOS/Pro Tools HD Identifier: com.digidesign.ProToolsHD Version: 8.1.1x59 (8.1.1d59) Code Type: X86 (Native) Parent Process: launchd [410] Date/Time: 2013-01-09 21:14:43.793 +0100 OS Version: Mac OS X 10.6.6 (10J567) Report Version: 6 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 90 Application Specific Information: abort() called Thread 0: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x00b290fa mach_msg_trap + 10 1 libSystem.B.dylib 0x00b29867 mach_msg + 68 2 com.apple.CoreGraphics 0x05399f29 _CGSOrderFrontConditionally + 145 3 com.apple.CoreGraphics 0x05399de4 CGSOrderFrontConditionally + 189 4 com.apple.HIToolbox 0x03b03b51 ReorderPlatformWindows + 698 5 com.apple.HIToolbox 0x03b0388a ReorderWindows(WindowContext*, __CFArray*, WindowData*, WindowData*, OpaqueWindowGroupRef*, OpaqueWindowGroupRef*, unsigned char) + 519 6 com.apple.HIToolbox 0x03b0344c ShiftWindowInList(WindowData*, OpaqueWindowGroupRef*, OpaqueWindowGroupRef*, WindowContext*, WindowData*, WindowData*) + 118 7 com.apple.HIToolbox 0x03b033b9 MoveWindowForward(WindowData*, WindowContext*, WindowData*, WindowData*, OpaqueWindowGroupRef*) + 71 8 com.apple.HIToolbox 0x03b032d2 BringWindowToFront(WindowData*, WindowContext*, OpaqueWindowGroupRef*, unsigned char) + 250 9 com.apple.HIToolbox 0x03b0a603 BringToFrontAndActivateWindow(WindowData*, OpaqueWindowGroupRef*, unsigned char) + 104 10 com.apple.HIToolbox 0x03b0a587 WindowData::SelectWindow() + 229 11 com.digidesign.framework.DFW 0x029f6a79 TWindow::PoseModally() + 75 12 com.digidesign.framework.DFW 0x02b2c3db TApplication::IsFrontProcess() + 4003 13 com.digidesign.framework.DFW 0x02b12e6f DFW_Alert::PoseAlert(DFW_Alert::EAlertType, std::string const&, std::vector<std::string, std::allocator<std::string> >&, std::vector<std::string, std::allocator<std::string> >*, long, long, long, bool*, std::string const*) + 1135 14 com.digidesign.framework.DFW 0x02b12fd0 DFW_Alert::Error(std::string const&) + 90 15 ...gidesign.framework.ProTools 0x0154e22d 0xdc1000 + 7918125 16 ...gidesign.framework.ProTools 0x0155d2ce 0xdc1000 + 7979726 17 com.digidesign.framework.DFW 0x02a38ad1 TEventHandler::HandleIdle(IdlePhase) + 131 18 com.digidesign.framework.DFW 0x02a2140f TApplication::Idle(IdlePhase) + 143 19 com.digidesign.framework.DFW 0x02a1f8f2 TApplication::MakeViewForAlienClipboard() + 68 20 com.digidesign.framework.DFW 0x02a74e27 DFW_Timers::LockedCallbackTimerProc:perator()(vo id*) + 55 21 com.digidesign.framework.DFW 0x02a73669 DFW_Timers::CallbackTimerManager::MasterCallback(v oid*) + 77 22 com.digidesign.framework.DFW 0x02a729d9 DFW_EventListener::NotifyListeners(std::list<DFW_E ventListener*, std::allocator<DFW_EventListener*> >&, DFW_EventListener::NotificationType, DFW_EventRef, DFW_EventTarget*) + 3419 23 com.digidesign.framework.DFW 0x02b31ed2 DFW_EventLoop::WaitForMouseUp(double) + 970 24 com.apple.CoreFoundation 0x03720adb __CFRunLoopRun + 8059 25 com.apple.CoreFoundation 0x0371e464 CFRunLoopRunSpecific + 452 26 com.apple.CoreFoundation 0x0371e291 CFRunLoopRunInMode + 97 27 com.apple.HIToolbox 0x03ac8004 RunCurrentEventLoopInMode + 392 28 com.apple.HIToolbox 0x03ac7dbb ReceiveNextEventCommon + 354 29 com.apple.HIToolbox 0x03c501a2 _AcquireNextEvent + 54 30 com.apple.HIToolbox 0x03c45e54 RunApplicationEventLoop + 228 31 com.digidesign.framework.DFW 0x02b31553 DFW_EventLoop::RunApplicationEventLoop() + 11 32 com.digidesign.framework.DFW 0x02a1fd6f TApplication::Run() + 45 33 ...gidesign.framework.ProTools 0x01a6c5dd LaunchProTools + 1567 34 com.digidesign.ProToolsHD 0x0000ad2c 0x1000 + 40236 35 com.digidesign.ProToolsHD 0x00004943 0x1000 + 14659 36 com.digidesign.ProToolsHD 0x00004871 0x1000 + 14449 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x00b4f982 kevent + 10 1 libSystem.B.dylib 0x00b5009c _dispatch_mgr_invoke + 215 2 libSystem.B.dylib 0x00b4f559 _dispatch_queue_invoke + 163 3 libSystem.B.dylib 0x00b4f2fe _dispatch_worker_thread2 + 240 4 libSystem.B.dylib 0x00b4ed81 _pthread_wqthread + 390 5 libSystem.B.dylib 0x00b4ebc6 start_wqthread + 30 0x00b566e2 thread_start + 34 Thread 90 Crashed: 0 libSystem.B.dylib 0x00b964fe __semwait_signal_nocancel + 10 1 libSystem.B.dylib 0x00b963e2 nanosleep$NOCANCEL$UNIX2003 + 166 2 libSystem.B.dylib 0x00c112aa usleep$NOCANCEL$UNIX2003 + 61 3 libSystem.B.dylib 0x00c329c8 abort + 105 4 libstdc++.6.dylib 0x03660fda __gnu_cxx::__verbose_terminate_handler() + 433 5 libstdc++.6.dylib 0x0365f17a __cxxabiv1::__terminate(void (*)()) + 10 6 libstdc++.6.dylib 0x0365f1ba __cxxabiv1::__unexpected(void (*)()) + 0 7 libstdc++.6.dylib 0x0365f2b8 __gxx_exception_cleanup(_Unwind_Reason_Code, _Unwind_Exception*) + 0 8 ...gidesign.framework.ProTools 0x01a6beb0 0xdc1000 + 13282992 9 libstdc++.6.dylib 0x0365f65a operator new(unsigned long) + 103 10 libstdc++.6.dylib 0x0365f703 operator new[](unsigned long) + 17 11 ...oontrack.superior.superior2 0x49e73351 NewMachOPlugIn + 1558113 12 ...oontrack.superior.superior2 0x49e73469 NewMachOPlugIn + 1558393 13 ...oontrack.superior.superior2 0x49e76580 NewMachOPlugIn + 1570960 14 ...oontrack.superior.superior2 0x49e74d12 NewMachOPlugIn + 1564706 15 ...oontrack.superior.superior2 0x49e02d73 NewMachOPlugIn + 1097859 16 ...oontrack.superior.superior2 0x49e15d4a NewMachOPlugIn + 1175642 17 ...oontrack.superior.superior2 0x49e164e7 NewMachOPlugIn + 1177591 18 ...oontrack.superior.superior2 0x49e171a9 NewMachOPlugIn + 1180857 19 ...oontrack.superior.superior2 0x49dcd048 NewMachOPlugIn + 877400 20 ...oontrack.superior.superior2 0x49de5c0f NewMachOPlugIn + 978719 21 libSystem.B.dylib 0x00b5685d _pthread_start + 345 22 libSystem.B.dylib 0x00b566e2 thread_start + 34 |
#2
|
||||
|
||||
Re: Help with this crash report!!
Hi,
Crash thread 90 toontrack superior drummer! Have you got the latest version of superior? Chris
__________________
PT MAC Troubleshooting... http://duc.avid.com/showthread.php?t=54888 Producer, Engineer, UKmastering Mixing & Mastering Blinders_Columbia top 40 UK album charts Slow Readers Club Joy Of The Return #9 UK album charts www.ukmastering.com PT10.3.10 Mountain Lion HD6 accel Magma PE6R4 D Command 32 MacPro 12 Core 3.46ghz UAD-2 Octo x2. Manley Vari-Mu, Manley Massive Passive, SSL VHD, ADL600, Grove Tubes ViPre, Tube-Tech CL-1B. Hafler TRM active monitoring. |
#3
|
|||
|
|||
Re: Help with this crash report!!
I have just had the same issue. PT keeps crashing when I try and open in Rosetta mode. I have searched and found suggestions to input code into Terminal to help install Rosetta and agree to license. It didn't help.
I would appreciate any assistance with this issue... Problem report lists: Crashed Thread: 34 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Pro Tools [4077] Thread 34 Crashed: 0 ??? 0x7ff8924c29a8 ??? 1 libsystem_kernel.dylib 0x7ff80287b202 __pthread_kill + 10 2 libsystem_pthread.dylib 0x7ff8028b2ee6 pthread_kill + 263 3 libsystem_c.dylib 0x7ff8027d9b45 abort + 123 4 libPTSL.dylib 0x14f6c87c6 cq_destroy_next(void*) + 86 5 libPTSL.dylib 0x14f6c8fa8 cq_next(grpc_completion_queue*, gpr_timespec, void*) + 1048 6 libPTSL.dylib 0x14f52e3f0 grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) + 80 7 libPTSL.dylib 0x14f4bd209 CPTSLServer::Run() + 601 8 libPTSL.dylib 0x14f4cc8da std::__1::__async_assoc_state<void, std::__1::__async_func<CPTSLServer::StartRunning() ::$_0>>::__execute() + 26 9 libPTSL.dylib 0x14f4cc97e void* std::__1::__thread_proxy<std::__1::tuple<std::__1: :unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct >>, void (std::__1::__async_assoc_state<void, std::__1::__async_func<CPTSLServer::StartRunning() ::$_0>>::*)(), std::__1::__async_assoc_state<void, std::__1::__async_func<CPTSLServer::StartRunning() ::$_0>>*>>(void*) + 62 10 libsystem_pthread.dylib 0x7ff8028b31d3 _pthread_start + 125 11 libsystem_pthread.dylib 0x7ff8028aebd3 thread_start + 15 |
#4
|
|||
|
|||
Re: Help with this crash report!!
**can a moderator please break this out into it's onw thread in the Pro Tools macOS subforum**
Uh lets see. No you don't have the same problem as in this thread from 2013 you posted to. That user is running Pro Tools HD/TDM on an now very old intel Mac with very different looking stack trace. You are running a recent version of Pro Tools on an Apple silicon mac. The only similarity is both applications crashed. You have no idea that these issues are related, and they are likely not. And you are posting this in the old legacy TDM subforum. Just not the right place, and likely to get you less help/visibility. Please in future create your own new thread for problems unless you are really sure the thread you are posting to is exactly the same issue. You also don't give any of the expected systems information. Read what is expected of you when asking for help here under the "Help us help you" link up the top of each DUC web page. You should be describing your mac model and config, macOS version, Pro Tools version and release date, audio interface and driver version, when in the startup Pro Tools crashes. When did this start happening? What changed around that time, etc. etc. Does this happen when you start up Pro Tools without a session open? Happens only when you open a session? Any session or specific sessions? "Help us help you" also describes the standard troubleshooting steps, some of which at least you should just be running through and trying before asking for help. And if that does not help when you do post describe clearly exactly what troublesooting you have tried. You should especially always just try trashing prefs (use Pete Gates PT Prefs2 tool to do this) when encountering a problem. Here I'd also test from a newly created admin account. I have no idea what exactly you mean by "insert code into terminal", or what you are talking about. Why not give links to exactly what else you have seen that you think is relevant instead of expecting people to guess what you are talking about or have done. As for this crash, the stack trace shows part of the new Pro Tools Scripting Language system being called. If you have any apps using that such as SoundFlow try uninstalling those apps and see if if that changes things. But you also likely need to just troubleshoot this more. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Crash Report... | Shifted Music | Pro Tools 10 | 3 | 02-17-2014 11:11 AM |
Crash report... | Shifted Music | Pro Tools 10 | 2 | 02-08-2014 02:02 PM |
Crash with PT 10.3.3 (crash report inside) | powerjoe | macOS | 8 | 01-22-2013 10:33 AM |
Best Crash Report ever!! | suicune | Pro Tools TDM Systems (Mac) | 10 | 07-14-2009 12:58 PM |
Major Crash with PT 7.3 cs5 crash report included | RuffJazzRecords | Pro Tools M-Powered (Win) | 0 | 02-09-2008 12:43 PM |