|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
How to read a crash report ?
Hi everyone,
In the studio where I'm currently working, PT "quits unexpectedly" way more than usual and I'm trying to understand why. The crash report is pretty big, I guess this is not good and I'm not sure to understand what it tells. Thank you ! PS: Sorry if my english isn't perfect Here is the crash report: Process: Pro Tools [220] Path: /Applications/Avid/*/Pro Tools.app/Contents/MacOS/Pro Tools Identifier: com.digidesign.ProTools Version: 10.3.2.47 (10.3.2f47) Build Info: Unknown-1032047~47 Code Type: X86 (Native) Parent Process: launchd [144] User ID: 501 Date/Time: 2013-04-16 19:24:11.327 +0200 OS Version: Mac OS X 10.8.2 (12C60) Report Version: 10 Interval Since Last Report: 612965 sec Crashes Since Last Report: 22 Per-App Interval Since Last Report: 400383 sec Per-App Crashes Since Last Report: 15 Anonymous UUID: 546272C7-6D66-4E39-3C72-7AF96EDA2DBF Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c4900000 VM Regions Near 0xc4900000: MALLOC_TINY 00000000c4700000-00000000c4900000 [ 2048K] rw-/rwx SM=PRV --> CG shared images 00000000c4a47000-00000000c4a4f000 [ 32K] rw-/rw- SM=SHM Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x929a7a2b memmove$VARIANT$sse42 + 206 1 com.audioease.Altiverb7.Digi 0x163684b4 std::vector<WalkieTalkie*, std::allocator<WalkieTalkie*> >::erase(__gnu_cxx::__normal_iterator<WalkieTalkie **, std::vector<WalkieTalkie*, std::allocator<WalkieTalkie*> > >) + 46 2 com.audioease.Altiverb7.Digi 0x16367d93 WalkieTalkie::MakeUndependant(WalkieTalkie*) + 59 3 com.audioease.Altiverb7.Digi 0x16367e9e WalkieTalkie::RemoveAllConnections() + 132 4 com.audioease.Altiverb7.Digi 0x16368156 WalkieTalkie::~WalkieTalkie() + 60 5 com.audioease.Altiverb7.Digi 0x16340f58 MissionCommand::~MissionCommand() + 152 6 com.audioease.Altiverb7.Digi 0x1657ea82 CmdWantsRecalc::~CmdWantsRecalc() + 78 7 com.audioease.Altiverb7.Digi 0x1634cc06 MissionHost::DoHandleCommand() + 758 8 com.audioease.Altiverb7.Digi 0x163e2aee MissionTimer_mac::Timer() + 124 9 com.apple.HIToolbox 0x9138754c TimerVector + 22 10 com.apple.CoreFoundation 0x920c89b6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUN CTION__ + 22 11 com.apple.CoreFoundation 0x920c8355 __CFRunLoopDoTimer + 709 12 com.apple.CoreFoundation 0x920ad162 __CFRunLoopRun + 1730 13 com.apple.CoreFoundation 0x920ac63a CFRunLoopRunSpecific + 378 14 com.apple.CoreFoundation 0x920ac4ab CFRunLoopRunInMode + 123 15 com.apple.HIToolbox 0x913771a7 RunCurrentEventLoopInMode + 319 16 com.apple.HIToolbox 0x914db7d0 GetNextEventMatchingMask + 92 17 com.apple.HIToolbox 0x914db74b GetNextEvent + 110 18 com.digidesign.framework.DFW 0x006f881a DFW_EventLoop::GetNextEvent(unsigned short, DFW_EventRef*) + 26 19 com.digidesign.framework.DFW 0x006f8e08 DFW_EventLoop::RunEventLoopUntilEmpty(long, unsigned short) + 168 20 com.digidesign.framework.DFW 0x005c0987 TStatusIndicator::Canceled(long long) + 1383 21 com.digidesign.framework.ProTools 0x0b7acaeb MFortressHWBPEntryPoint_exit_mfort6317_ + 5843281 22 com.digidesign.framework.ProTools 0x0b82e411 MFortressHWBPEntryPoint_exit_mfort6317_ + 6374007 23 com.digidesign.framework.ProTools 0x0b7b61c7 MFortressHWBPEntryPoint_exit_mfort6317_ + 5881901 24 com.digidesign.framework.ProTools 0x0b858d84 MFortressHWBPEntryPoint_exit_mfort6317_ + 6548458 25 com.digidesign.framework.ProTools 0x0b829a28 MFortressHWBPEntryPoint_exit_mfort6317_ + 6355086 26 com.digidesign.framework.ProTools 0x0b9288a9 MFortressHWBPEntryPoint_exit_mfort6317_ + 7399183 27 com.digidesign.framework.ProTools 0x0b90e09e MFortressHWBPEntryPoint_exit_mfort6317_ + 7290628 28 com.digidesign.framework.ProTools 0x0c1a492c MFortressHWBPEntryPoint_exit_mfort6317_ + 16295826 29 com.digidesign.framework.DFW 0x005a1d67 TFileHandler::DoRead(bool) + 39 30 com.digidesign.framework.DFW 0x005a2391 TFileHandler::ReadFile(bool) + 65 31 com.digidesign.framework.DFW 0x005a391d TFileBasedDocument::ReadDocument(bool) + 125 32 com.digidesign.framework.ProTools 0x0c1a3b73 MFortressHWBPEntryPoint_exit_mfort6317_ + 16292313 33 com.digidesign.framework.ProTools 0x0c0fec7f MFortressHWBPEntryPoint_exit_mfort6317_ + 15616741 34 com.digidesign.framework.DFW 0x005c5826 TODocCommand::DoIt() + 54 35 com.digidesign.framework.DFW 0x005935eb TCommandHandler::PerformCommand(TCommand*) + 187 36 com.digidesign.framework.DFW 0x00593f3f TCommand::Process() + 31 37 com.digidesign.framework.DFW 0x005899ea TApplication::ProcessEvent(TEvent*) + 26 38 com.digidesign.framework.DFW 0x0058a300 TApplication::WakeUp() + 64 39 com.digidesign.framework.DFW 0x006ef92b TApplication::CreateNewOSApplication(void*, void*, void*) + 667 40 com.apple.HIToolbox 0x914cbb6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 41 com.apple.HIToolbox 0x91353594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343 42 com.apple.HIToolbox 0x91352980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430 43 com.apple.HIToolbox 0x913527ca SendEventToEventTargetWithOptions + 94 44 com.apple.HIToolbox 0x91386b7e ToolboxEventDispatcherHandler(OpaqueEventHandlerCa llRef*, OpaqueEventRef*, void*) + 3108 45 com.apple.HIToolbox 0x91353a3f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538 46 com.apple.HIToolbox 0x91352980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430 47 com.apple.HIToolbox 0x91366855 SendEventToEventTarget + 88 48 com.apple.HIToolbox 0x914cb267 ToolboxEventDispatcher + 82 49 com.apple.HIToolbox 0x914cb129 RunApplicationEventLoop + 240 50 com.digidesign.framework.DFW 0x006f8e6b DFW_EventLoop::RunApplicationEventLoop() + 11 51 com.digidesign.framework.DFW 0x00589abd TApplication::Run() + 45 52 com.digidesign.framework.ProTools 0x0cc27fc8 MFortressHWBPEntryPoint_exit_mfort6317_ + 27319854 53 com.digidesign.framework.ProTools 0x0cc29749 LaunchProTools + 1305 54 com.digidesign.ProTools 0x0000f317 0x1000 + 58135 55 com.digidesign.ProTools 0x0001041a 0x1000 + 62490 56 com.digidesign.ProTools 0x0000f09d 0x1000 + 57501 |
#2
|
||||
|
||||
Re: How to read a crash report ?
Hi,
Altiverb!! Have you got the latest version? 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: How to read a crash report ?
Yes we have the latest version (7.0.5)
PT's version is 10.3.2, should we update to 10.3.4 ? |
#4
|
||||
|
||||
Re: How to read a crash report ?
Quote:
It's always advised to run the latest version with the latest fixes! Not sure that is going to fix this? In altiverb are you loading a IR called walkie talkie? Can't tell for sure but that could be causing the problem if that IR is corrupted somehow? I would look at reinstalling Altiverb and all the IRs and trashing any prefs to do with audioease and altiverb. Library / prefs and user library prefs delete them. Then reinstall everything altiverb and IRs 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. |
#5
|
|||
|
|||
Re: How to read a crash report ?
Yes I saw that this IR was mentioned in the report and I found it strange because it's not used in the session.
The other strange fact is that this morning we had a new report and Altiverb is no longer mentioned. Anyway, I'll follow your advices and keep you inform. Thank you ! Here is the report of this morning : Process: Pro Tools [259] Path: /Applications/Avid/*/Pro Tools.app/Contents/MacOS/Pro Tools Identifier: com.digidesign.ProTools Version: 10.3.2.47 (10.3.2f47) Build Info: Unknown-1032047~47 Code Type: X86 (Native) Parent Process: launchd [143] User ID: 501 Date/Time: 2013-04-17 09:21:16.321 +0200 OS Version: Mac OS X 10.8.2 (12C60) Report Version: 10 Interval Since Last Report: 615226 sec Crashes Since Last Report: 25 Per-App Interval Since Last Report: 401086 sec Per-App Crashes Since Last Report: 18 Anonymous UUID: 546272C7-6D66-4E39-3C72-7AF96EDA2DBF Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000f8ea0000 VM Regions Near 0xf8ea0000: CG backing stores 00000000c5861000-00000000c58d3000 [ 456K] rw-/rw- SM=SHM --> Submap 00000000ffff0000-00000000ffff1000 r--/r-- process-only submap Application Specific Information: objc_msgSend() selector name: release dyld: in dladdr() Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x93a91a9c objc_msgSend + 44 1 com.apple.CoreFoundation 0x9207e93b CFRelease + 171 2 com.apple.CoreFoundation 0x920a79cb -[__NSArrayM dealloc] + 251 3 libobjc.A.dylib 0x93aaa8ff -[NSObject release] + 47 4 com.apple.CoreFoundation 0x9207e93b CFRelease + 171 5 com.apple.CoreFoundation 0x920ad171 __CFRunLoopRun + 1745 6 com.apple.CoreFoundation 0x920ac63a CFRunLoopRunSpecific + 378 7 com.apple.CoreFoundation 0x920ac4ab CFRunLoopRunInMode + 123 8 com.apple.HIToolbox 0x913771a7 RunCurrentEventLoopInMode + 319 9 com.apple.HIToolbox 0x914db7d0 GetNextEventMatchingMask + 92 10 com.apple.HIToolbox 0x914db74b GetNextEvent + 110 11 com.digidesign.framework.DFW 0x006f881a DFW_EventLoop::GetNextEvent(unsigned short, DFW_EventRef*) + 26 12 com.digidesign.framework.DFW 0x006f8e08 DFW_EventLoop::RunEventLoopUntilEmpty(long, unsigned short) + 168 13 com.digidesign.framework.DFW 0x005c0987 TStatusIndicator::Canceled(long long) + 1383 14 com.digidesign.framework.ProTools 0x0d067aeb MFortressHWBPEntryPoint_exit_mfort6317_ + 5843281 15 com.digidesign.framework.ProTools 0x0d0ee103 MFortressHWBPEntryPoint_exit_mfort6317_ + 6393705 16 com.digidesign.framework.ProTools 0x0d0711c7 MFortressHWBPEntryPoint_exit_mfort6317_ + 5881901 17 com.digidesign.framework.ProTools 0x0d113d84 MFortressHWBPEntryPoint_exit_mfort6317_ + 6548458 18 com.digidesign.framework.ProTools 0x0d0e4a28 MFortressHWBPEntryPoint_exit_mfort6317_ + 6355086 19 com.digidesign.framework.ProTools 0x0d1e38a9 MFortressHWBPEntryPoint_exit_mfort6317_ + 7399183 20 com.digidesign.framework.ProTools 0x0d1c909e MFortressHWBPEntryPoint_exit_mfort6317_ + 7290628 21 com.digidesign.framework.ProTools 0x0da5f92c MFortressHWBPEntryPoint_exit_mfort6317_ + 16295826 22 com.digidesign.framework.DFW 0x005a1d67 TFileHandler:oRead(bool) + 39 23 com.digidesign.framework.DFW 0x005a2391 TFileHandler::ReadFile(bool) + 65 24 com.digidesign.framework.DFW 0x005a391d TFileBasedDocument::ReadDocument(bool) + 125 25 com.digidesign.framework.ProTools 0x0da5eb73 MFortressHWBPEntryPoint_exit_mfort6317_ + 16292313 26 com.digidesign.framework.ProTools 0x0d9b9c7f MFortressHWBPEntryPoint_exit_mfort6317_ + 15616741 27 com.digidesign.framework.DFW 0x005c5826 TODocCommand:oIt() + 54 28 com.digidesign.framework.DFW 0x005935eb TCommandHandler::PerformCommand(TCommand*) + 187 29 com.digidesign.framework.DFW 0x00593f3f TCommand::Process() + 31 30 com.digidesign.framework.DFW 0x005899ea TApplication::ProcessEvent(TEvent*) + 26 31 com.digidesign.framework.DFW 0x0058a300 TApplication::WakeUp() + 64 32 com.digidesign.framework.DFW 0x006ef92b TApplication::CreateNewOSApplication(void*, void*, void*) + 667 33 com.apple.HIToolbox 0x914cbb6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 34 com.apple.HIToolbox 0x91353594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343 35 com.apple.HIToolbox 0x91352980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430 36 com.apple.HIToolbox 0x913527ca SendEventToEventTargetWithOptions + 94 37 com.apple.HIToolbox 0x91386b7e ToolboxEventDispatcherHandler(OpaqueEventHandlerCa llRef*, OpaqueEventRef*, void*) + 3108 38 com.apple.HIToolbox 0x91353a3f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538 39 com.apple.HIToolbox 0x91352980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430 40 com.apple.HIToolbox 0x91366855 SendEventToEventTarget + 88 41 com.apple.HIToolbox 0x914cb267 ToolboxEventDispatcher + 82 42 com.apple.HIToolbox 0x914cb129 RunApplicationEventLoop + 240 43 com.digidesign.framework.DFW 0x006f8e6b DFW_EventLoop::RunApplicationEventLoop() + 11 44 com.digidesign.framework.DFW 0x00589abd TApplication::Run() + 45 45 com.digidesign.framework.ProTools 0x0e4e2fc8 MFortressHWBPEntryPoint_exit_mfort6317_ + 27319854 46 com.digidesign.framework.ProTools 0x0e4e4749 LaunchProTools + 1305 47 com.digidesign.ProTools 0x0000f317 0x1000 + 58135 48 com.digidesign.ProTools 0x0001041a 0x1000 + 62490 49 com.digidesign.ProTools 0x0000f09d 0x1000 + 57501 |
#6
|
|||
|
|||
Re: How to read a crash report ?
Quote:
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Crash with PT 10.3.3 (crash report inside) | powerjoe | macOS | 8 | 01-22-2013 10:33 AM |
HD native Error Report - AVID, you need to read this! | Andi R | Pro Tools HDX & HD Native Systems (Mac) | 18 | 05-10-2012 05:35 AM |
Can anyone read and understand this crash report ? | mafiacondon | Pro Tools TDM Systems (Mac) | 4 | 10-03-2011 11:32 AM |
Please read and give some feedback on this report | izzy_white | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 8 | 03-13-2009 09:34 AM |
Major Crash with PT 7.3 cs5 crash report included | RuffJazzRecords | Pro Tools M-Powered (Win) | 0 | 02-09-2008 12:43 PM |