AAE-9173 - Ran Out Of CPU Power

[earthling5615]

Just throwing this out there... I've read a lot of the posts in this thread and haven't seen this offered: Pro Tools seems to have a memory leak. If it sits overnight, the CPU usage meter on a session goes from (example) 15% to 85%. I get the dreaded -9173 immediately. Restarting PT usually remedies. When that fails, restarting the computer fixes it. On a couple of occasions, I've had to also restart the HD I/O (8 x 8).

If it takes a long time for PT to start, I understand why you wouldn't want to restart, but taking one or more of the steps above always fixes the issue here.

*********
MacPro (trashcan) 6 core, 32 GB, PT HDX running 12.8.1 on Sierra. 1TB SSD, 1TB SSD ext drive, 2TB spinning drive for backup of everyday work, 4TB Time Machine. NI Komplete 10 Ultimate, AIR Complete, MachFive 3, More plugs than you can shake a stick at...

[Downtown_BE]

Originally Posted by earthling5615

Just throwing this out there... I've read a lot of the posts in this thread and haven't seen this offered: Pro Tools seems to have a memory leak. If it sits overnight, the CPU usage meter on a session goes from (example) 15% to 85%. I get the dreaded -9173 immediately. Restarting PT usually remedies. When that fails, restarting the computer fixes it. On a couple of occasions, I've had to also restart the HD I/O (8 x 8).

If it takes a long time for PT to start, I understand why you wouldn't want to restart, but taking one or more of the steps above always fixes the issue here.

*********
MacPro (trashcan) 6 core, 32 GB, PT HDX running 12.8.1 on Sierra. 1TB SSD, 1TB SSD ext drive, 2TB spinning drive for backup of everyday work, 4TB Time Machine. NI Komplete 10 Ultimate, AIR Complete, MachFive 3, More plugs than you can shake a stick at...

I´ve experienced the same - even if I work on a session for a while with exactly the same plugs and everything I start getting -9073 after a while.. I actually thought it might be a processor heat problem too

[gmu]

Now that I'm on PT 2018 I may be getting fewer of these errors. Certain sessions do seem to specifically having this issue. The difference now is that when I'm working on one of those sessions, after about the 3rd time the error occurs the playback engine goes all wonky and the audio sounds like it's all been put through a crazy bit crusher...super distorted with weird harmonic time shifted artifacting. It requires a shut down and restart of PT.

I don't think this ever happened before 2018.

MBP 2015 3.1ghz i7 16gb ram High Sierra
Pro Tools 2018-1
UAD Thunderbolt Apollo 8p

[MusicMadness]

After 11 month of struggling with my maxed out MacBook Pro 2015 I decided to sell it and buy Mac Pro 2013. I managed to do it within the same price range and that was insanely good decision. One of my previous sessions I managed to save on laptop was spiking just after start and there was that awful distortion happening so I had to relaunch Pro Tools. With a bit of luck the playback last 5 s - 20 s before 9173. Now the same session works perfectly with CPU stress 25% ± 5%. Another one that could crash PT with 9173 was official demo session. It was working fine until CPU was cool but after some time it kept crashing. Now the same session takes 8-12% of CPU. For everyone having troubles with 2015 MacBook Pro I strongly recommend switch to Mac Pro.

[~ufo~]

i'd like to offer my two cents on this.

I have a HD Native system om a 2012 3.33 6 Core Mac Pro.

It ran quite beautifully on PT9 and PT 10.
I could record bands at 96k 64 samples with a few plugs with hardly any issues.
It was very rare that I had to bump to 128 samples because of errors.

Since PT11 my experience has deteriorated significantly, I seem to recall it became unusable to record for me at around 11.7 to the point where I can't reliably record a single track in PT at 96k 64 buffer without even a single plugin loaded. Show stopping CPU errors galore.
I fact, the track count or plugin count don't seem to matter much.
At least, a session recording one track seems to run about as undependable as a session recording 64 tracks. Plug ins is a different story, of course, but I'm getting errors even without active plugins.
Now I've talked to several people are Avid about this and there appears to be an issue between MacOS and PT. It also appears that not every mac suffers from it.
I found out, by chance, that PT runs MUCH better on my machine on Windows 8.1 than it does on MacOS. So I've been running most sessions on Windows for the past year.
I keep updating my Mac Partition, hoping that they've fixed it and I keep sharing my findings with Apple support, but no luck so far.

If you can, I would recommend installing a Win8.1 partition and testing if your system performs better on it. It's not ideal, but it turned my unusable system into a useable system again.

Good luck.

[Sounds]

fyi iv joined the 9173 club , went from PT 11 to protools 2018.3 then 2018.4.

FYI - as many have said PT 9 ran better.

[mikeyman]

in PT's 10 in the Performance engine there is a box to check if you don't want the notice to pop up when you record or playback.I just checked mine and no more notice running at 40% usage meter

[Sounds]

yeah PT 10 was weird like that! some session worked better with it check, then other , unchecked! lol

[spookybuk]

I made a clean reinstall of my windows (I used Windows 7 pro 64x and now I installed Windows 10 pro 64x). I was running Pro Tools 12.3 and downloaded the 12.5 and installed it on the new Windows.

So I have a clean and new Install. I use an SSD for Windows and a WD Black Caviar as the recording hard drive. My processor is a Intel 17-5820k, with no overclocking. I have 32gb ram and a Quadro video card.

I'm getting CPU spikes interrupting my recording in a project with 5 plugins overall. System usage is between 1 and 5%, but it spikes all the way and after reading about it, I know I'll have to downgrade.

I guess the "official" solution is also very clear - if you want to fix it, you have to give them more money.

Pro Tools is an amazing software. It's a pity it doesn't work.

[albee1952]

Originally Posted by [email protected]

Buffer siZe is the same. 1024. You're missing the point of the post. BOTH these sessions are running off of the same drive with same layout with very different results.
Just to entertain- Mac is a late 2012 12 core MacPro with 24GB of ram.
Record drive is a 1TB SSD with 200GB free.

24GB is an odd amount of RAM(to me) so if you have sticks of different sizes, that may be hurting performance. Also, 2.4GHz is a tad on the slow side for cpu speed(upgrading to 3.33 or 3.46GHz processors might yield a nice boost, but I would also hit OWC and get 64GB of matching RAM) Is Trim enabled on the SSD?

With 2 sessions acting differently from the same drive, you need to look at what plugins are in the slow session, that are not in the fast session I see that you said they are the same(so I understand and share your confusion). Does either have hidden tracks? Any audio in either session?