Crash – crash – crash this, can’t be normal

[Kris Merkel]

Does PrPro just crash and quit or are you experiencing Kernel Panics causing your whole system to go down. You will see decreased performance if your memory pool settings are not allocated correctly.

Something to try is to troubleshoot application by application and see if you can identify which portion of your workflow is causing the crashes.

I am going to go out on a limb and guess that you have a bad stick of RAM in your system. I could be wrong but you could play with the RAM config and amount.

When you did your installs did you install PrPro first after the OS?

“Think of everything in terms of building capacity.”

Kris Merkel
twitter: @kris_merkel
Product Manager, Flanders Scientific Inc.
http://www.shopfsi.com
Co-Founder, Atlanta Cutters Post Production User Group
http://www.atlantacutters.com

2.2Ghz MBP core i7
16Gb RAM
CS6/FCP7
AJA T-Tap
AJA IO XT
FSI LM-2461W/CM-170W

[Alex Rod]

thank you for helping Kris.

I don’t think it’s bad memory because the OS or any of the other software don’t crash.

PPro has quit unexpectedly a couple of times, but that’s rate. What’s more common is the “not responding” message when I open the force quit window.
So I just sit and wait several minutes. Sometimes the software comes back by itself and responds, but most of the time, it just hangs unresponsive. At that point I have to force quit it.

So what is the rule of thumb when it comes to allocating the right amount of memory for pPro, AE, ME, and encore.

Is there a best practice article that I can read?

again, thank you!

[Gerald Goldman]

I have found that Media Encoder and Dynamic Link grab a lot of system resources and, over time, kill the performance of my machine. A strategic reboot is often necessary.

I have stopped trying to run Media Encoder in the background as I work on other projects. Fortunately, my deadlines allow me to leave batches rendering overnight.

If someone finds a good processor/memory allotment strategy, I hope they will share.

Gerald Goldman
Director of Post Production
Grace Creek Media
http://www.gracecreek.com
http://www.sportskool.com

[Kris Merkel]

Adobe handels the allocation of memory for the installed apps, you can choose how much or little goes into this pool as opposed to how much is reserved for other applications.

Since you are not experiencing kernel panics i would guess that the installed sticks of RAM are also not the problem. In you memory Prefs, how much of your 32GB of RAM are shared by the Adobe apps and how many GBs are reserved for other applications?

“Think of everything in terms of building capacity.”

Kris Merkel
twitter: @kris_merkel
Product Manager, Flanders Scientific Inc.
http://www.shopfsi.com
Co-Founder, Atlanta Cutters Post Production User Group
http://www.atlantacutters.com

2.2Ghz MBP core i7
16Gb RAM
CS6/FCP7
AJA T-Tap
AJA IO XT
FSI LM-2461W/CM-170W

[Kris Merkel]

Responding to Gerald, I find the same behavior on my machine that I cannot do much of anything else, even browsing the web quickly while AME is running a job. My specs are rather paltry compared to the OP so I would expect that is normal behavior if your memory pool is heavily weighted towards the running Adobe apps.

“Think of everything in terms of building capacity.”

Kris Merkel
twitter: @kris_merkel
Product Manager, Flanders Scientific Inc.
http://www.shopfsi.com
Co-Founder, Atlanta Cutters Post Production User Group
http://www.atlantacutters.com

2.2Ghz MBP core i7
16Gb RAM
CS6/FCP7
AJA T-Tap
AJA IO XT
FSI LM-2461W/CM-170W

[Erik Lindahl]

My experience with Premier Pro CS6 is anything but stable / reliable sadly. Very odd bugs at home (2012 iMac, nVidia GPU, BlackMagic I/O) and at the studio (2008 MacPro, AMD GPU, AJA I/O).

Perhaps not any help but you’re defiantly not alone in having issues with PrPro.

PS, IL, AE and AME I however haven’t had any issues with on any system. Version x.0 tends to have a bug or two you need to dodge but that’s it. Premier seems to be Adobes black sheep – at least on OSX.

[Ryan Holmes]

@Gerald – if you’re running OSX 10.7 or later use the “Purge” command via Terminal to free up system resources. Does the same thing as a system reboot without the hassle of rebooting.

https://ryanholmes.me/cutcolorpost/2013/2/24/terminal-purge

I’ve long believed that either AME or Dynamic Link has some sort of a memory leak, because if I leave it working over night by the morning I’ll have about 200MB free out of 24GB of RAM. Doesn’t seem right.

@Alex – I’ve experienced some of this as well. You may also make sure that all your permissions are correct as AME may be getting hung on trying to access a file. You may also look at cleaning out your Media Cache Database. In any Adobe app go to Preferences–>Media–>Clean. That can help scrub some of the junk away.

If it’s an important job I’ve found that exporting out a self-contained movie from PPro and bringing that into AME in order to run my variety of deliverables works better than just queing a job from PPro (and using Dynamic Link….FCP to Compressor had some of the same problems in that regard).

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Joe Sheffer]

I have similar problems. I find I spend more time trouble shooting my mac than I do using it at the moment. It’s been a nightmare since mid 2011 ish. I don’t think I remember a single week without something similar happening on my work station. My only conclusion is software/hardware has got to complicated in the last few years.

[Alex Rod]

The exporting a self contained movie defeats the purpose of productivity. To me, the whole idea is that you can export while still edit. By exporting a self contained from ppro then using it to do another export in AME means that I wont be able to use ppro while exporting the self contained AND while exporting the deliverable in AME… Ouch!
I sadly feel that the ppro suite (excluding AE) wants to be professional, but can’t truly handle the professional workload… I want to be proven wrong on this more than anything…because i really dont want to have to go to avid, but at the same time I have work that has to get done and don’t want to deal with crash after crash.
I will make network four of my machines and make a render farm for AE and use one of the machine exclusively for AME and DV authoring .
Plus introduce the purging and other constant system work arounds to my daily habits.
If anyone can add something to this, please share.

Let’s formally contact adobe as a group with these issues. I think they are good listeners.

[Alex Rod]

and another crash…making a very simple DVD in Encore – Just raw footage with a one button menu. Encoding stopped. No crash message, no “not responding” on the force quit menu…nothing.

Encore is just not encoding at all…what gives?!