|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
||||
|
||||
Re: assertion errors how to fix
Quote:
Removing them is usually enough! although trashing the prefs will make sure the cache is empty before rebooting pro tools. The last few things you changed!! sounds a bit of a coincidence so i would concentrate on them. Ram? can you remove half the ram and try? then switch ram around to the half you removed etc! 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. |
#12
|
|||
|
|||
Re: assertion errors how to fix
Here is another "crash" item:
Exception Type: EXC_BREAKPOINT (SIGABRT) Exception Codes: 0x0000000000000001, 0x0000000000000000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x91d1dc5a __kill + 10 1 libSystem.B.dylib 0x91d1dc4c kill$UNIX2003 + 32 2 libSystem.B.dylib 0x91db05a5 raise + 26 3 libSystem.B.dylib 0x91dc66e4 abort + 93 4 libstdc++.6.dylib 0x9554cfda __gnu_cxx::__verbose_terminate_handler() + 433 5 libstdc++.6.dylib 0x9554b17a __cxxabiv1::__terminate(void (*)()) + 10 6 libstdc++.6.dylib 0x9554b1ba __cxxabiv1::__unexpected(void (*)()) + 0 7 libstdc++.6.dylib 0x9554b1ca __cxxabiv1::__unexpected(void (*)()) + 16 8 libstdc++.6.dylib 0x9554ac59 __cxa_call_unexpected + 67 9 ...design.framework.FileFormat 0x00a31ac5 BDM_Globals::Release() + 101 10 ...gidesign.framework.ProTools 0x152aefd2 MFortressHWBPEntryPoint_exit_mfort6317_ + 27317320 11 ...gidesign.framework.ProTools 0x152b0749 LaunchProTools + 1305 12 com.digidesign.ProTools 0x0000f317 0x1000 + 58135 13 com.digidesign.ProTools 0x0001041a 0x1000 + 62490 14 com.digidesign.ProTools 0x0000f09d 0x1000 + 57501 |
#13
|
|||
|
|||
Re: assertion errors how to fix
Quote:
EXC_BREAKPOINT (SIGABRT)
__________________
David Hughes Sound Designer shineonstudio.com Mac Pro 2 x 2.4GHz Quad Core Intel Xeon, 14GB 1066 MHz DDR3, Avid OMNI HD (Rev A), Digidesign 192, Pro Tools HD v. 10.3.9 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
assertion errors that aren't going away | dobatron81 | Pro Tools TDM Systems (Mac) | 1 | 03-20-2009 06:09 PM |
Assertion errors? | DarthFader777 | Post - Surround - Video | 10 | 02-17-2009 10:18 AM |
neo assertion errors help | rboos4 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 15 | 07-29-2008 09:02 AM |
Assertion Errors? | Chaka015 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 7 | 06-26-2007 08:51 AM |
Anyone else get Assertion Errors? | beggehorn | Pro Tools TDM Systems (Win) | 4 | 12-01-2003 11:53 PM |