DP constant crashing/Log file 9.02

mrgkeys · Post by **mrgkeys** » Sat May 14, 2016 12:25 pm

Recently moved to a new iMac 5K from an old Mac Pro and things have chugged along fine for a bit, but now I am getting constant crashes doing several different things. changing aux busses, writing automation, copying plugins to different tracks, duplicating a mix, sometimes just opening a file. It's different files, old and new. From DP3 up to DP 9.02. It's crashed more in the last week than in the last 10 years for me.. I'm almost sure it's a plugin, but it's hard to tell without a crash log. I see the Motu crash report popup and I send them on, but is there no way to see the DP crash log anymore? Did it go away? I've tried all the usual fixes, from permissions to preferences, loading into a new file.. DP user for 20+ years, I know my way around the program.. The Console logs don't give up any information. If I could just see the DP crash log, I'd have a better chance of getting to root of it. It's a fresh install, I didn't migrate anything to the new machine. Fresh installs of 400+ plugins (that's a lot of logins and password and auth codes..). PT, Logic and S1 v3 all work great, it's not a driver problem. I have an RME Madi FX in a thunderbolt enclosure, UAD Octo thunderbolt, etc.. The Processor meter barely moves, I love the machine.. would just like to get the bugs out. The Mac Pro is not an option to go back to. Any ideas on how to see the crash log? Is there a preference for seeing it in the MOTU crash reporter? There used to be a DP log in the Console, but I don't see it anymore, unless it's moved to a different place. All 96k projects. Thoughts?

mikehalloran · Post by **mikehalloran** » Sat May 14, 2016 5:06 pm

You can have Console up when this happens. Everything is time stamped.

You can also have the background activity window open in DP.

One or another should give you a clue.

mrgkeys · Post by **mrgkeys** » Sun May 15, 2016 11:25 am

There used to be a detailed Digital Performer crash log. It's gone. No longer in the Console logs. The main Console log only ever says this.

5/15/16 1:09:09.798 PM Digital Performer[640]: 13:09:09.798 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
5/15/16 1:09:09.897 PM Digital Performer[640]: Digital Performer(640,0x7fff74e9f000) malloc: *** error for object 0x10a840a08: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
5/15/16 1:09:14.942 PM WindowServer[184]: disable_update_timeout: UI updates were forcibly disabled by application "MOTU Crash Reporter" for over 1.00 seconds. Server has re-enabled them.

I'd just like to look at DP's crash log.. I can't find a preference or a way to enable it.. I know it gets sent to MOTU. I don't think it's available to the end user any longer. And that's bad for me at the moment. as the crashes every 5 minutes or so are getting irritating. I"m gonna set autosave to every 1 min so I won't lose what I've just done.. Today's project is a different one, same crashes, it has to be out by Friday.. grrr. I am going to try a fresh install over my fresh install again. Anyone every had a Commands pref file corrupted? In trashing the prefs, I kept that one.. I have a heavily customized keyboard shortcut file.. I'd like to not start over there if I could. But I will if y'all think it could be root of the problem.

stratology · Post by **stratology** » Sun May 15, 2016 12:51 pm

I'm on DP8, El Cap, I can see the full crash logs in Console, under 'User Diagnostic Reports'.
The physical location of the DP crash logs displayed in Console is ~/Library/Logs/DiagnosticReports.

More DP reports (not the crash logs) are in 'System Diagnostic Reports'.

Crash logs are searchable in Console, so you can look for keywords like 'Error', 'crash' etc.
Here's a good description of how to read crash logs.

Another neat troubleshooting trick is that you can select 'Show all messages' in Console, click the 'Clear Display' button, and then immediately reproduce the issue. You can see the log entries being written as the issue occurs.

You can tell if the issue is caused by a 3rd party plug in quite easily, without reading logs. Go to /Library/Audio/Plug-Ins, here you will find the folders for the Audio Units (called 'Components') and VST plug ins. Start with the type that you use primarily in DP. If it's AUs, open the Components folder, and move all Audio Units into a folder on your Desktop. Then test. If the issue disappears, move the plug-ins back, in a split-half approach: you move half of the plug ins, test, if there's no problem you move half of the remaining plug ins, test, etc.

mrgkeys · Post by **mrgkeys** » Sun May 15, 2016 2:42 pm

gotta be a DP9 thing then.. there are no logs in any of those places for a DP that's crashed 25+ times in the last 2 days. The reports are there in System Diagnostic Reports, but as you said, those are not crash logs. I know I saw those logs in DP8, maybe 9 just doesn't log them locally and just sends them to MOTU? After a reinstall, I tried a test file today with no AU plugins (with a new machine and fresh installs, I opted not to put any VSTs on the machine) and copying an aux send crashed it, as did removing aux send from the mini menu. Copying a plugin with the option key drag method does it as well. Got my first snapshot automation is not working properly problem today too... starting to miss the old Mac Pro. My next guess now is maybe a piece of bad ram, I have 32 gigs, I'll try pulling some. I moved my live project over to MixBuss 32C, which is stupidly awkward, but allows me to use all my plugins and not crash and I've been wanting to try it out. I haven't had a crash in PT, Logic or S1v3, and I've done the same sized projects in all 3. So I'm not for sure it's the machine. Maybe the MOTU gods will bless us with a 9.2 soon.

a Console search just reveals these, over and over and over.. while the second one doesn't bother me, I know it's all about hosting as many plugins as possible, the first explains the crappy windowing performance.. The 4 gig video card should run all those windows just fine..

WindowServer[187]: disable_update_timeout: UI updates were forcibly disabled by application "Digital Performer" for over 1.00 seconds. Server has re-enabled them.

Digital Performer[481]: 15:07:54.938 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.

Thanks for the ideas and the help. I'm always thankful for this board.

stratology · Post by **stratology** » Sun May 15, 2016 3:45 pm

No crash logs are odd, every app should create them. If you suspect bad RAM, you can test for it by running Apple Diagnostics. Hold down the D key during boot. IIRC, there should be a 'quick' and a more comprehensive RAM test - run the quick one first, the comprehensive test can take quite some time.

From your tests, it does not look like a plug in related issue.

After running the hardware test, you can do some systematic troubleshooting to find out what's going on - see if issues only occur in DP or in other apps as well, etc. Instructions here and here.

These are general steps. One DP specific thing I'd try is to see if the crashes occur when no peripherals (like your audio interface, external disks, etc) are connected.

mikehalloran · Post by **mikehalloran** » Sun May 15, 2016 4:07 pm

Let's start with the basics.

Did you do a fresh install of the OS and use Time Machine or Migration Assistant or did you clone to create your current system?

When you installed DP, did you install in the default location?

mrgkeys · Post by **mrgkeys** » Sun May 15, 2016 10:07 pm

yes and yes..

mrgkeys · Post by **mrgkeys** » Sun May 15, 2016 10:11 pm

removed all AUs as well. It crashed a bit less. I did a quick RAM check today and it seems to be fine.. 32 gigs takes a while. Sometimes it's wildly repeatable. And sometimes not. Also happens with the built in sound, the Orion over USB and the RME MADI FX in a thunderbolt enclosure.

mrgkeys · Post by **mrgkeys** » Tue May 17, 2016 2:07 pm

some good news! MOTU crash reporter crashed!! Which sounds bad, but it's good, because I got to see the crash report!! maybe MOTU's crash reporter hijacks the regular reporting.. I don't know.. But here it is.. I just put the crashed threads in.. here's the good bits.. crashing today on bouncing to disk, saving file, and quitting program. Along with crashing for no reason in the middle of a tune..

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x00007fff85ca66d9 CFHash + 297
1 com.apple.CoreFoundation 0x00007fff85ca10fe __CFBasicHashRehash + 2158
2 com.apple.CoreFoundation 0x00007fff85ca7146 __CFBasicHashAddValue + 86
3 com.apple.CoreFoundation 0x00007fff85ca867d CFDictionarySetValue + 221
4 com.apple.CoreFoundation 0x00007fff85cda2d6 __71+[CFPrefsSource withSourceForIdentifier:user:byHost:container:perform:]_block_invoke63 + 678
5 com.apple.CoreFoundation 0x00007fff85cd93ea +[CFPrefsSource withSourceForIdentifier:user:byHost:container:perform:] + 970
6 com.apple.CoreFoundation 0x00007fff85cd9010 -[CFPrefsSearchListSource addSourceForIdentifier:user:byHost:container:] + 128
7 com.apple.CoreFoundation 0x00007fff85cd2f96 __73+[CFPrefsSearchListSource withSearchListForIdentifier:container:perform:]_block_invoke + 518
8 com.apple.CoreFoundation 0x00007fff85cd2af3 +[CFPrefsSearchListSource withSearchListForIdentifier:container:perform:] + 579
9 com.apple.CoreFoundation 0x00007fff85d272d7 CFPreferencesAppSynchronize + 23
10 com.apple.speech.synthesis.framework 0x00007fff8e05a2c5 TalkingAlertsEnabled + 42
11 com.apple.AppKit 0x00007fff898cdb64 -[NSAlert startTimerForSpeaking] + 85
12 com.apple.AppKit 0x00007fff89a2026d __19-[NSAlert runModal]_block_invoke + 68
13 com.apple.AppKit 0x00007fff898c8c1c -[NSAlert runModal] + 139
14 OSFoundation.dylib 0x0000000101f45fa3 DialogUtils::AlertDialog::Run(bool) + 563
15 HiLevelWrappers.dylib 0x0000000101ec52d4 PerfNavigationServices::GetSoundFileImportInfo(FileSpecification const&) + 62228
16 com.motu.DigitalPerformer 0x00000001001fbee8 TimeRegionOf<Tick>::Add(TimeRangeOf<Tick>) + 892808
17 com.motu.DigitalPerformer 0x00000001001fd5d6 TimeRegionOf<Tick>::Add(TimeRangeOf<Tick>) + 898678
18 com.motu.DigitalPerformer 0x0000000100012f43 0x100000000 + 77635
19 DPBasicUI.dylib 0x000000010198c564 Application::TryToCloseAllDocuments() + 68
20 com.motu.DigitalPerformer 0x00000001008ec30f boost::shared_ptr<MotuFuture<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > MotuJobQueueAddJob<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >(blocking_queue<boost::shared_ptr<MotuJobQueueJob> >&, boost::function<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > ()> const&) + 131599
21 com.motu.DigitalPerformer 0x00000001008eb942 boost::shared_ptr<MotuFuture<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > MotuJobQueueAddJob<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >(blocking_queue<boost::shared_ptr<MotuJobQueueJob> >&, boost::function<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > ()> const&) + 129090
22 DPBasicUI.dylib 0x0000000101966f25 RequestHandler::HandleCommand(RequestHandler*, CommandSpecifier const&, CommandActivator const*) + 85
23 DPBasicUI.dylib 0x000000010198cae2 Application::HandleCommand(CommandSpecifier const&, CommandActivator const*) + 18
24 DPBasicUI.dylib 0x0000000101966f25 RequestHandler::HandleCommand(RequestHandler*, CommandSpecifier const&, CommandActivator const*) + 85
25 DPBasicUI.dylib 0x0000000101975d1c ChainOfCommand::Chore::Run() + 748
26 DPBasicUI.dylib 0x00000001019765f6 ChainOfCommand::HandleBeforeCommands::~HandleBeforeCommands() + 1638
27 libMotuCoreLibs.dylib 0x00000001015fda87 CIdleChore::IdleAndReturnNextIdleTime() + 375
28 OSFoundation.dylib 0x0000000101f6bc65 IdleOnExit::~IdleOnExit() + 21
29 PerfFoundation.dylib 0x0000000102a1dda4 AppEventFilter::HandleUIEvent(UIEvent&) + 132
30 OSFoundation.dylib 0x0000000101fd79fc OS::EventImpl::DispatchToApplication(UIEvent, boost::optional<MotuOSWindow::OSWindow&>) + 428
31 OSFoundation.dylib 0x0000000101f91451 RunApplicationWithDelegate(int, char**, std::__1::auto_ptr<MOTUApplicationDelegate>&) + 7073
32 com.apple.AppKit 0x00007fff897f4cfa -[NSApplication _docController:shouldTerminate:] + 69
33 com.apple.AppKit 0x00007fff897f4b98 __91-[NSDocumentController(NSInternal) _closeAllDocumentsWithDelegate:shouldTerminateSelector:]_block_invoke + 534
34 com.apple.AppKit 0x00007fff897f4787 -[NSDocumentController(NSInternal) _closeAllDocumentsWithDelegate:shouldTerminateSelector:] + 1309
35 com.apple.AppKit 0x00007fff897f4243 -[NSDocumentController(NSInternal) __closeAllDocumentsWithDelegate:shouldTerminateSelector:] + 291
36 com.apple.AppKit 0x00007fff897f3f17 -[NSApplication _shouldTerminate] + 705
37 com.apple.AppKit 0x00007fff897f366d -[NSApplication terminate:] + 762
38 libsystem_trace.dylib 0x00007fff8634e07a _os_activity_initiate + 75
39 com.apple.AppKit 0x00007fff89846dbd -[NSApplication sendAction:to:from:] + 460
40 com.apple.AppKit 0x00007fff89846b57 -[NSMenuItem _corePerformAction] + 336
41 com.apple.AppKit 0x00007fff898468b7 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114
42 libsystem_trace.dylib 0x00007fff8634e07a _os_activity_initiate + 75
43 com.apple.AppKit 0x00007fff898457a5 -[NSMenu performKeyEquivalent:] + 357
44 OSFoundation.dylib 0x0000000101fc3988 AdjustLightness(HSLAColor const&, double, double) + 1464
45 com.apple.AppKit 0x00007fff89844949 -[NSApplication _handleKeyEquivalent:] + 920
46 com.apple.AppKit 0x00007fff8976b0fe -[NSApplication sendEvent:] + 4274
47 OSFoundation.dylib 0x0000000101f90694 RunApplicationWithDelegate(int, char**, std::__1::auto_ptr<MOTUApplicationDelegate>&) + 3556
48 com.apple.AppKit 0x00007fff895d1df2 -[NSApplication run] + 796
49 com.apple.AppKit 0x00007fff8959b368 NSApplicationMain + 1176
50 OSFoundation.dylib 0x0000000101f8fa38 RunApplicationWithDelegate(int, char**, std::__1::auto_ptr<MOTUApplicationDelegate>&) + 392
51 com.motu.DigitalPerformer 0x00000001008f1d81 boost::shared_ptr<MotuFuture<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > MotuJobQueueAddJob<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >(blocking_queue<boost::shared_ptr<MotuJobQueueJob> >&, boost::function<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > ()> const&) + 154753
52 com.motu.DigitalPerformer 0x0000000100b1aee2 void BroadcastMessage<Video::TimebaseListener, void (double, double), double&, double&>(std::__1::common_type<Provider<Video::TimebaseListener>*>::type, void (Video::TimebaseListener::*)(double, double), double&&&, double&&&) + 848994
53 com.motu.DigitalPerformer 0x0000000100b1ae01 void BroadcastMessage<Video::TimebaseListener, void (double, double), double&, double&>(std::__1::common_type<Provider<Video::TimebaseListener>*>::type, void (Video::TimebaseListener::*)(double, double), double&&&, double&&&) + 848769

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00007fff8604f37f rbx: 0x0000000000000000 rcx: 0x00007fff85ca65b0 rdx: 0x0000000000000001
rdi: 0x0000000000000000 rsi: 0x0000000000000005 rbp: 0x00007fff5fbfcd50 rsp: 0x00007fff5fbfcd40
r8: 0x0000000000000000 r9: 0x0000000000000003 r10: 0x0000000000000000 r11: 0x0000000102c10910
r12: 0xffffffffffffffff r13: 0x00000001072db280 r14: 0x0000000000000000 r15: 0x0000000000000009
rip: 0x00007fff85ca66d9 rfl: 0x0000000000000246 cr2: 0x000000010399cd40

Logical CPU: 4
Error Code: 0x00000000
Trap Number: 3

mikehalloran · Post by **mikehalloran** » Tue May 17, 2016 2:57 pm

Are you using Mailmate or Electon?

YouTube · Post by **James Steele** » Tue May 17, 2016 3:42 pm

HOW TO DISABLE MOTU CRASH REPORTER

At some point, MOTU built in their own crash reporter that produces a dialog on a crash and then sends reports directly back to MOTU. This is a good thing as it helps MOTU find problems more quickly, but for the user who wants to try to troubleshoot, it can be inconvenient.

IMPORTANT: I would stress only using this when having a recurring problem and needing to investigate. Otherwise, allow the reports to go to MOTU. They get a lot of valuable information to fix bugs the way it is, so don't disable as standard practice.

I can tell you two ways to disable it.

First the difficult way:

You type in the following into the Terminal window:

Code: Select all

arch -x86_64 "/Applications/Digital Performer.app/Contents/MacOS/Digital Performer" --disable_crash_reporter &

Hit "Enter" and this will then launch DP with the MOTU crash reporter disabled.

Now the EASIEST way: (acknowledgment to David Das who taught me this.)

• Download this very small file: http://motunation.com/files/Disable_DP9 ... ommand.zip

• Unzip and find the file "Disable DP9 Crash Reporter.command" and place in Apps folder.

• Optional: You can then click and drag that file to the right (documents) side of the Dock

• Click on it, and it will automatically run the Terminal command and launch DP9 with the MOTU crash reporter disabled. Any crashes that then happen during this session will generate crash reports in the normal location. (The script does not quit the Terminal app after launching DP9. If that bothers you, manually quit Terminal after DP9 has launched.)

• As a reminder, you MUST launch DP this way EACH TIME to disable the MOTU crash reporter, so DP will create crash reports on your hard drive. If you quit DP and then run again without using the Terminal command, crash reports will go directly to MOTU again.

Timeline · Post by **Timeline** » Tue May 17, 2016 6:49 pm

Good to know James. Thanks!

mrgkeys · Post by **mrgkeys** » Wed May 18, 2016 10:23 am

Well, some good news and weird news.. First off thank you James for posting that Terminal command.. it works excellent.. So the weird news first.. I opened DP without the Crash Reporter and I worked for almost 10 hours without a crash (last night and today)!! WTH? I finished 2 mixes, so yay.. I get paid. Nothing I did seemed to make it even behave strangely.. Chasing auxes, dragging plugins, bouncing to disk, editing of any kind.. all perfect. But the good news is. finally today quitting for lunch, I had a crash on quit!! Yay!! the offender is the Hornet VU Meter in thread 0!. I have the Klangheim VU meter I can replace it with, not a problem at all. I like the Auto function of the Hornet, but since I have those gain adjustments already, I can just type them into the Klangheim.. Thanks everyone, I'll let you know what happens from here. I'll pass on the crash log to Hornet too..

mrgkeys · Post by **mrgkeys** » Wed May 18, 2016 10:25 am

also, it would be nice if MOTU would reenable the crash reports for us as well as phoning them home.. something for 9.2 I hope. Most people never look at them or know where to even go and see them, so really the only folks they're hiding them from are the people who do need them and can use them.

MOTUnation.com