DP 7.1 unstable and jumpy :(

[KEVORKIAN]

Crashed Thread: 16


Thread 16 Crashed:
0 com.motu.MAS.framework 0x017efdd3 0x17bd000 + 208339
1 com.motu.MAS.framework 0x01823a86 0x17bd000 + 420486
2 com.motu.MAS.framework 0x0182508d 0x17bd000 + 426125
3 com.motu.MAS.framework 0x01825145 0x17bd000 + 426309
4 libSystem.B.dylib 0x98d72fbd _pthread_start + 345
5 libSystem.B.dylib 0x98d72e42 thread_start + 34

I'm running out the door right now, but I cropped the important parts in to the quote above.

Thread 16 crashed and it appears to have something to do with the MAS framework.

Have you tried booting with plugins disabled?
You may also wish to try removing MAS plugins .

[bjornln]

Crashed Thread: 16


Thread 16 Crashed:
0 com.motu.MAS.framework 0x017efdd3 0x17bd000 + 208339
1 com.motu.MAS.framework 0x01823a86 0x17bd000 + 420486
2 com.motu.MAS.framework 0x0182508d 0x17bd000 + 426125
3 com.motu.MAS.framework 0x01825145 0x17bd000 + 426309
4 libSystem.B.dylib 0x98d72fbd _pthread_start + 345
5 libSystem.B.dylib 0x98d72e42 thread_start + 34

I'm running out the door right now, but I cropped the important parts in to the quote above.

Thread 16 crashed and it appears to have something to do with the MAS framework.

Have you tried booting with plugins disabled?
You may also wish to try removing MAS plugins .

Or, check the drivers for your Audio interfaces...

/B

[ironchef_marc]

I'll try disabling the MAS plugins tomorrow. I use a 2408 mk3 and I do have the latest drivers for it.
Thanks for the suggestions!

[Shooshie]

From what I'm guessing, as a completely uneducated and unqualified Crash Log Analyzer (newly appointed as of this sitting ) it would appear that a group of audio strings got poured directly into the output without buffering or queuing with a "semaphore wait trap." All other threads show either the buffering or wait trap. This one does not, and it's the one that crashed. Thread 16:

Thread 14:
0 libSystem.B.dylib 0x98d459ee mach_wait_until + 10
1 ...ple.CoreServices.CarbonCore 0x97026034 MPDelayUntil + 43
2 ...ple.CoreServices.CarbonCore 0x97035a56 Delay + 107
3 ...opellerheads.rewire.library 0x241637e8 RWPUnregisterDeviceImp +
21574
4 ...opellerheads.rewire.library 0x2417ea5c RWPUnregisterDeviceImp +
132794
5 libSystem.B.dylib 0x98d72fbd _pthread_start + 345
6 libSystem.B.dylib 0x98d72e42 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x98d45916 semaphore_wait_trap + 10
1 com.motu.MAS.framework 0x01805d69 0x17bd000 + 298345
2 com.motu.MAS.framework 0x018250c4 0x17bd000 + 426180
3 com.motu.MAS.framework 0x01825145 0x17bd000 + 426309
4 libSystem.B.dylib 0x98d72fbd _pthread_start + 345
5 libSystem.B.dylib 0x98d72e42 thread_start + 34
Thread 16 Crashed:
0 com.motu.MAS.framework 0x017efdd3 0x17bd000 + 208339
1 com.motu.MAS.framework 0x01823a86 0x17bd000 + 420486
2 com.motu.MAS.framework 0x0182508d 0x17bd000 + 426125
3 com.motu.MAS.framework 0x01825145 0x17bd000 + 426309
4 libSystem.B.dylib 0x98d72fbd _pthread_start + 345
5 libSystem.B.dylib 0x98d72e42 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x98d45916 semaphore_wait_trap + 10
1 com.motu.MAS.framework 0x01805d69 0x17bd000 + 298345
2 com.motu.MAS.framework 0x018250c4 0x17bd000 + 426180
3 com.motu.MAS.framework 0x01825145 0x17bd000 + 426309
4 libSystem.B.dylib 0x98d72fbd _pthread_start + 345
5 libSystem.B.dylib 0x98d72e42 thread_start + 34

Now, what that implies, or even whether I'm in the ballpark of a good guess, would have to be determined by MOTU or someone here with programming skills. SixStringGeek? You around?

Shooshie

[Killahurts]

I can't believe you guys are sifting through code here.

It don't work right, K?

[James Steele]

I did notice Radio Gal is on a PPC machine. I too am on a dual G5 and I have noticed that one project that played fine in DP 7.02 got processor spikes in 7.1. I ended up having to change Work Priority to "Low" (from "Medium" where it was set in 7.02) in order to get rid of the spiking. Maybe this is something affecting G5 users more.

[Frodo]

I did notice Radio Gal is on a PPC machine. I too am on a dual G5 and I have noticed that one project that played fine in DP 7.02 got processor spikes in 7.1. I ended up having to change Work Priority to "Low" (from "Medium" where it was set in 7.02) in order to get rid of the spiking. Maybe this is something affecting G5 users more.

Hey James:

I just did an offline survey of this thread. Everyone reporting the stuttering symptoms appears to be on PPC, except for delcosmos-- who is on Intel and reported a crash. The OP wasn't reporting crashes but stutters, which leads me to believe that delcosmos' case might be solved under different circumstances.

I hope I haven't overlooked anyone, but the stats at first glance were interesting.

[Shooshie]

Starting to be a pretty strong pattern, I'd say. But if anyone is using 7.1 on a PPC without problems, then that tends to say it's not the hardware, but the stuff loaded on that hardware, which in this case would mean plugins. Old computers often have old plugins, simply because they never required and update. It's worth checking that out.

But James seems to have a whole different approach that might also solve the problems. Slipping that Work Priority down to Low just might yield some benefits.

[amergin]

I'd generally recommend looking for non motu stuff in a crash log, otherwise we'd all be getting it. Perhaps "spectrasonics.amber" points to something happening with a spectrasonics plugin. Did a google search and there are a few other references to logic crashing with this phrase in the crashlog. Try removing any spectrasonics stuff and retrying.

[Radiogal]

Sure, but still, DP 7.02 works without any problem and no crashes..

[twistedtom]

So people using it on a Intel are doing fine with 7.1? I have been afraid to install after reading this topic.

[jimagine]

I haven't pushed it to the limit in any way, but on my i7 quad it's all good so far.

[ironchef_marc]

I'm on Intel and I'm having problems.

[frankymax]

Yeah, I used 7.1 yesterday for quite a while and experienced a few crashes which were not happening in 7.02. I have disabled auto-save to make sure it isn't the culprit and I've sent my crash logs to MOTU for them to check out, but I'm on an Intel Mac and so far Spectrasonics Omnisphere seems to be a bit unhappy (crashes when changing outputs from a buss to main outs)but Stylus RMX seems OK; Lexicon Plug-ins are kind of buggy and crashing (but that could be their new updater which I just installed). When I start a fresh project and don't open a 7.02 project it seems more stable, but many of my templates and projects are in 7.02. I'm kind of thinking I'll stick with 7.02 for any "real" work I have to do and monkey around with 7.1 and keep sending in crash logs as they crop up. I really like some of the new features on 7.1 but it's not worth hassling with until they can determine what's going on here.

Again, I'm on an Intel Mac.

[BobK]

Where can I find the crash logs?

Two places: Launch Apple's 'Console' app, in your Applications->Utilities folder. If you don't see two columns in the main window, click on 'Show Log List'. In the left column, crash reports are listed under LOG FILES -> /Library/Logs -> CrashReporter.

You can locate the actual log in the finder by control-clicking on the log's title and selecting 'Reveal in Finder' (or type command-R).

The actual location of the logs in the Finder is: (user name)/Library/Logs/CrashReporter