Automation edits crash PT 7.3.1cs2 during playback.

[holden]

This is the 6th time in the past month that PT has crashed during automation edits. In all cases I have been editing automation during playback. In the most recent instance I was editing level automation for a 2-track (audio) group.

The problem is inconsistent in that I usually edit automation during playback without incident.

After each crash I've reported my activities to Apple in the Apple diagnostics window that pops up. I thought it was time I posted the problem here.

The frequency of the problem does not appear to be changed by the standard debugging procedure as outlined in the General Troubleshooting sticky.

Digi- Please address this problem.

[crizdee]

After each crash I've reported my activities to Apple in the Apple diagnostics window that pops up.

Have you looked at the crash log? and can you see which thread has crashed?? it will usually say near the top of the report which thread crashed!! then scroll down to that thread and see what it says, it might give an idea of what the problem is!

you can copy and paste the crash report here and let others have a look. they are stored here ... mack HD/Users/your name/library/logs/crash reporter/pro toos HD crash.log.

my money's on a plugin out of date!

Chris

[holden]

Hi Chris-
Thank you for your help.
The listing from Pro Tools HD.crash.log follows. Thread 17 is implicated. I see no reference there to a plugin, but then I am unfamiliar with the interpretation of such logs.
Regards,
Holden

**********

Host Name: Mac-Pro
Date/Time: 2007-03-28 20:09:52.097 -0700
OS Version: 10.4.9 (Build 8P2137)
Report Version: 4

Command: Pro Tools HD
Path: /Applications/Digidesign/Pro Tools/Pro Tools HD.app/Contents/MacOS/Pro Tools HD
Parent: WindowServer [385]

Version: 7.3.1cs2 (7.3.1f125)

PID: 524
Thread: 17

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0000004c

.
.
.

Thread 17 Crashed:
0 com.digidesign.ProToolsHD 0x0049de22 start + 4830326
1 com.digidesign.ProToolsHD 0x0049e30e start + 4831586
2 com.digidesign.ProToolsHD 0x0049fd82 start + 4838358
3 com.digidesign.ProToolsHD 0x004a2097 start + 4847339
4 com.digidesign.ProToolsHD 0x0093cc62 start + 9675446
5 com.digidesign.ProToolsHD 0x004b0a96 start + 4907242
6 com.digidesign.ProToolsHD 0x004b0d2c start + 4907904
7 com.digidesign.ProToolsHD 0x007e72ec start + 8276288
8 ...gn.framework.CoreFoundation 0x028b6f55 Sys_RawThreadTimerTask::Exec() + 109
9 ...gn.framework.CoreFoundation 0x028b6e72 Sys_RawThreadTask::Run() + 60
10 ...gn.framework.CoreFoundation 0x0286a6d8 Sys_RawThread::GetCurrentThreadID() + 112
11 ...ple.CoreServices.CarbonCore 0x90cb8f94 PrivateMPEntryPoint + 51
12 libSystem.B.dylib 0x90024147 _pthread_body + 84

.
.
.

Thread 17 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x3f989200 ecx: 0x3f9894f8 edx: 0x00000000
edi: 0x00000000 esi: 0xffffff6a ebp: 0xb0aa7c28 esp: 0xb0aa7bc0
ss: 0x0000001f efl: 0x00010202 eip: 0x0049de22 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

[holden]

Digi-
Any insights, comments, preventative measures, plans for a fix, recognition of problem for this?
Thanks.

[srsonido]

Holden, you are not alone!

I'm seeing the same behavior: I'll be mixing along in real time - adjusting automation while playing back and for no apparent reason PT will lock up briefly (spinning beach ball of death) then crash / exit abruptly. If I try to re-open immediately, without rebooting the system, about 50% of the time I will get a gray screen OSX lock up and have to do a hard power cycle.

I was first seeing this behavior after upgrade to 7.2 - I had no such problems in 6.9 - so I just tried the upgrade to 7.3.1 hoping that it would resolve this issue. No luck. Today's session began to manifest the same symptoms.

Very, very, very annoying! This problem is preventing me from mixing down in a normal manner and slowing down my work considerably. Perhaps if Digi sees this issue is not isolated they will give it some mind share. I will also be posting a bug report.

For the record I have verified that all my Waves plugins are current (did that with the initial upgrade to 7.2), and, in fact, my most recent crash happened when changing the level automation on a track that had no inserts and output directly to the audio 1/2 outputs - no bussing.


I have also run the error logs and posted the crashed threads - see below.

Any insights?

Thanks!

---------------------------


Thread 14 Crashed:
0 com.digidesign.ProToolsHD 0x004f53d0 start + 5188832
1 com.digidesign.ProToolsHD 0x004f5a54 start + 5190500
2 com.digidesign.ProToolsHD 0x004f6938 start + 5194312
3 com.digidesign.ProToolsHD 0x004f8f84 start + 5204116
4 com.digidesign.ProToolsHD 0x009c12dc start + 10218476
5 com.digidesign.ProToolsHD 0x005092f4 start + 5270532
6 com.digidesign.ProToolsHD 0x00509400 start + 5270800
7 com.digidesign.ProToolsHD 0x00864d30 start + 8791616
8 ...gn.framework.CoreFoundation 0x02ac3dc8 Sys_RawThreadTimerTask::Exec() + 216
9 ...gn.framework.CoreFoundation 0x02ac3bbc Sys_RawThreadTask::Run() + 108
10 ...gn.framework.CoreFoundation 0x02a70024 Sys_RawThread::GetCurrentThreadID() + 132
11 ...ple.CoreServices.CarbonCore 0x90bc48b0 PrivateMPEntryPoint + 76
12 libSystem.B.dylib 0x9002b508 _pthread_body + 96

.
.
.


Thread 14 crashed with PPC Thread State 64:
srr0: 0x00000000004f53d0 srr1: 0x100000000000f030 vrsave: 0x0000000000000000
cr: 0x24002424 xer: 0x0000000000000000 lr: 0x00000000004f53c4 ctr: 0x000000009012b1bc
r0: 0x00000000004f53c4 r1: 0x00000000f080f940 r2: 0x0000000000000000 r3: 0x0000000000000001
r4: 0x0000000000000000 r5: 0x000000002f5371c0 r6: 0x000000000c2854c2 r7: 0x0000000000000000
r8: 0x00000000f080fb48 r9: 0x0000000032ddf3e4 r10: 0x0000000000000000 r11: 0x0000000002b2098c
r12: 0x000000009012b1bc r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x0000000000000001 r22: 0x00000000f080fb50 r23: 0x0000000001580000
r24: 0x00000000f080fb5c r25: 0x00000000ffffffc6 r26: 0x0000000000000000 r27: 0x0000000000000000
r28: 0x000000000c2854c2 r29: 0x000000000c2854c2 r30: 0x000000002f536e00 r31: 0x000000002f536e00

[holden]

Digi? Any help on this?

[Mike Thornton]

You both are not alone. I have been having the same problem too. Whilst adjusting automation I get the spinning wheel of death, during which PT continues to play, then crash. I have always been able to reboot Pro Tools and go to the Session Backups folder and open the last saved copy of the session.

My system
Dual 1.42Ghz PowerPC G4 machine with 2 gig of ram running Mac OS 10.4.8 with PT 7.3.1cs2

Any ideas folk?

[DigiTechSupt]

Those crash reports aren't helpful - they don't tell us much other than Pro Tools crashed.

How, exactly, are you editing automation? Can you give me an idea of the size and composition of your sessions? Are you using video in your session? What number and types of drives are you using? Are you absolutely, positively sure that all plug-ins are PT7 compatible - as in you've compared them manually against the compatibility grid on our website?

Any pertinent details you can provide about your configuration, usage, etc. will help us in trying to reproduce the problem.

[Mike Thornton]

In my case, editing has been on client's firewire 400 buss powered drives with Oxford 911 chipset.

It has always happened whilst I have been modifying volume automation with the mouse whilst PT is playing back. Sessions not large 30 min radio doc with 6 to 8 audio tracks, very basic.

Will revisit plug-in list to double check but I did check when I first installed 7.3.

Only started happening since installing 7.3.1cs2. It didn't happen with cs1 or earlier.

Hope that helps,

[studiojimi]

this is making me afraid to update to 7.3.1cs2


why is digi paying so much attention to the icon issues used by a few
instead of the everyday issues used by many?

i can't see how any beta tester who one would supposedly putting heart an emotion into their mix and testing PT with all the brands of plugs out there in the session at the same time would not be feeling remorse at the loss of time and creativity when the crashes are happening.


is a single 3G processor machine enough these days with PT?


it may not be.

stabiltiy please and consistantly please