-9173 error in PT 12

[ArKay99]

Yep, just got it a little while ago. Had my playback engine set to 256 samples and worked all day. Then went to bounce in realtime, got about 1 minute in and blurrrpp... -9173 error, ran out of cpu power, use less plugins, blah, blah, blah. Before that cpu was hovering around 16% with spikes to about 28%. Then...

Spinning beachball of death and cpu meter acting like a horizontal yo-yo. Had to force quit and do over, after I set the playback buffer to 1024, finished ok.

It was a session I started on PT10 vanilla...

[mixgate]

turn on dynamic processing - higher buffer setting also a plug-in maybe causing it Slate FGX for example

[ArKay99]

Originally Posted by mixgate

turn on dynamic processing - higher buffer setting also a plug-in maybe causing it Slate FGX for example

Thanks. I know about all that stuff. I don't have any Slate plugs. I did have Sansamp on a track, but I put POWR Dither before. So either that doesn't work either or it was something else. If I had freeze track I could have used that, I could have just bounced it in real time...

This isn't one of those things that causes me stress any longer as Pro Tools is no longer my primary DAW. I thought -9173 was addressed in PT12...

[john1192]

more of the same crap .. a re-write of code .. really !! posted this in another thread as well .. we have been duped into thinking it will get better .. piling on of old code is Lazy ..

[rinky]

"It's Back!" for me as well this weekend. No Sansamp, just the typical Waves plugins, a couple of VIs and VE Pro slave. The error occurred during midi recording then alas, the code of death! Trashed prefs, reboot and all's fine... for now.

[albee1952]

Yeah, this is why I hit Save before bouncing.....

[cjwalker]

Just had this happen to me too. PT crashes if I even try to do an offline bounce. And the other day I noticed a bug in the field recorder guide track. If your on yosemite when you go to select areas to search in you just get a blank window meaning you can't tell PT where to search. Frustrating!

[davidr17]

I recently purchased and installed Pro Tools 12.5.0 after having used Pro Tools 9 for years with no problems. I have a brand new kick@$$ computer that is running at 1-2% CPU utilization until it instantly spikes to 100% out of nowhere and throws the -9173 error. This happens constantly and even on simple sessions with only 2 or 3 tracks. Pro Tools 12 is essentially unusable for me. The only clue I can find is this event in event viewer about 2-3 minutes before the -9173 error hits:

Fault bucket 129056631416, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: ProTools.exe
P2: 12.5.0.395
P3: 10.0.10586.2.0.0

which tells me that Pro Tools 12.5.0.395 has a memory leak (I'm a software developer -- trust me on this). I'm going to try downloading and installing 12.4 as someone in this thread recommended and see if that works.

[TAMBOR]

Originally Posted by davidr17

I recently purchased and installed Pro Tools 12.5.0 after having used Pro Tools 9 for years with no problems. I have a brand new kick@$$ computer that is running at 1-2% CPU utilization until it instantly spikes to 100% out of nowhere and throws the -9173 error. This happens constantly and even on simple sessions with only 2 or 3 tracks. Pro Tools 12 is essentially unusable for me. The only clue I can find is this event in event viewer about 2-3 minutes before the -9173 error hits:

Fault bucket 129056631416, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: ProTools.exe
P2: 12.5.0.395
P3: 10.0.10586.2.0.0

which tells me that Pro Tools 12.5.0.395 has a memory leak (I'm a software developer -- trust me on this). I'm going to try downloading and installing 12.4 as someone in this thread recommended and see if that works.

Would it be possible for you to open a case with Avid with this info? We have been seeing this 9173 problem for a while now (do a forum search), and this is the first time anyone has found any "hard evidence" on something like a memory leak.

Everyone has suspected some screwed up code in at least 12.5, but of course the user community has the burden of proof...

[stanonbass]

Yeah 12 is pretty much a disaster. I mean lets not sugar coat it.