The Mac CS6 "Serious Error" thread

[needles27]

It looks like there are 4-6 disjointed threads about some big problems Mac users are finding with CS6 (and 6.0.1)  To give us a better place to figure out solutions and for others to find with a search, maybe we can post a discussion here.

The Adobe engineers are participating and receiving crash logs, and hopefully a pattern can develop.

I'm on a MacPro 4,1, Lion 10.7.4, CS6.0.1, 32GB RAM, GTX 285 with the latest nVidia and CUDA drivers.  I am seeing 2 primary issues:

Lots of Serious Error crashes.  This happens without any noticeable pattern - sometimes with the title tool, trim monitor, or simply just scrubbing the timeline.  It seems to happen more frequently with Dynamic Links in the timeline.  Also, I believe it is happening more often (or maybe exclusively)  with the MPE GPU option enabled.  I think in Software Only mode, it may not be present, although further testing required.

Also, I am having an issue where Pr will display black only in the source and program monitors, unless I click around the timeline and will get flashes of images.  This is remedied by changing over to Software Only for the MPE.  It seems to be worse if Safari is running.

Wil - an Adobe engineer - has taken a look at my crash logs and seems to think something is funky with the graphcs drivers in both cases, but crash logs from other users seem to not agree. 

CS6 on the mac - for  me and a few others - is incredibly flaky.  If you are having issues, can you post and explain what you are seeing and what your hardware/driver config is.  Any patterns we can find will help the engineers troubleshoot and get this taken care of. 

[Jeremy_Saville]

Cuda is 5.0.17. And yes still getting the sereious errors and screen going black. I'm on Mountain Lion.  It's quirky, you never know when it's going to start up, the other day I went for a few hours without a crash, but I wasn't using it much at that time.  It's just very nerve racking when you're trying to work. It comes down to being able to trust your tool.

[Kevin-Monahan]

We are continuing to attack the bugs brought up on this thread. I was just speaking with engineering this morning, they want to make sure we have bugs filed for every issue. Please make sure you file a bug report, if you have repeatable steps, even better. Random crashes are harder to pin down, but still file a bug if it happens to you. File it here: http://www.adobe.com/go/wish

[Jim Curtis]

Just wondering, Kevin... do the crash logs you've been getting tell you anything?  Should we be sending them when we get a crash?  Seems like they'd tell you a lot more than a non-repeatable bug report.

[DeeDeeDean]

Hi,

I spent a lot of money on a 2 day course on PP6 run in an IMAC. The program crashed constantly and the Instrucor, a Certified Adobe Instructor, had no idea what was going on. I have sinced purchased a brand new,newly released and  very expensive MAC BOOK PRO with the Nvidia Card and 8 gig Ram and installed Mountain Lion as well. I am using a GTECH 2 Terbabyte 0 Raid External Hard Drive. So far no "Serious Error" crashes. However, most of myProject  Media is OFFLINE with big red render line on Timeline. I tried to re-connect but cannot.

I read here in Adobe that this has something to do with numbering Hard Drives (?) and the path being messed up. I am using a one month trial of PP6 since I refuse to purchase this priduct until l I am reassured that it will work. If  not, I wil cal up Apple and buy FCP 7 via phone order.

If any knows how to re-link the media, I am all ears! I am not a technie and have zero interested in rebuilding computers. I just want to edit my projects!

Thank You!

Mari D.

[Jim Curtis]

Welcome to the forum, DDD.

This thread is for the Serious Error messages.  If you're not getting them, then please start a new thread, or join one with your specific issue.  Thank you.  Look up "relink" in on-line help.

[Jonah Lee Walker]

I ended up with a couple of crashes yesterday, but not the same ones I was getting with the GTX 285, but that is compared to 16 crashes in almost no time with the GTX 285. SO my system is a whole lot more stable with QUADRO FX 4800.

[andycorleone]

Any new About this?  I'm in a Macpro I recently upgade to ML (I did an clean install) but I'm still have "Serious Error"   not sure if there is something to do with this but my error is very easy to replicate:

1)Run and Nvidia card on mac my is a GTX 285

2)Imports 60p (59.94 fps)  MTS footage from a Panasonic GH2 or Sony FS100, NEX-5N or VG20

3)interprate it as 23.976

play with it in Premiere open After Effects check Safari etc in a matter of few minutes you will get a "Serious Error" I can't belived this thread has been open for so long and there are not signs of hopes   I'm very sad to swich back to FCP or need to start learning AVID

[ExactImage]

Disable the CUDA support for your GTX285 and things get a lot better.   Yes, I know, it's not ideal, it's not what Adobe promised, but hey, it's a workaround for now.

C'mon Adobe, let's have a fix, or at least some indication that you are working on it and it 'will' be fixed in a 6.0.x update and not a 6.5.x release.  If it's not fixed in a 6.0.x update you will lose me (and I suspect many others) as a customer.  Period.  End of story. So, what's the score?

[bossy22]

I am really speechless, that

a) This hasn't been discovered during development. I mean, do they test the stuff they program?? This is happening to so  many people and there aren't that many configs on the mac platform. Not like windows and thats rock solid.

b) That they haven't figured anythingout yet.. The thread started in June, right??

unbelieveable...

[genefama]

bossy, Not true, some progress was made.  We were accused of being whiners and conspiracy theorists!  ;-O

[EditorPete]

C'mon guys....the negativity won't get you/us anywhere. We all understand your frustrations. I've been running fine for a while now without any major crashes. Just no MPE. Go back to 5.5 if you can't handle waiting around for MPE.

[genefama]

Adobe admitted they were ignoring us and would keep doing so until we re-listed every complaint that we had already spent weeks listing in exhaustive detail--as if we were starting from scratch. Now you say quit complaining. Me, I just want to not have to re-link and re-render the same media everyday.

[Guest]

Just submitted my REPEATABLE crash to Adobe.  Can someone else try to emulate this crash on their mac?  If so please submit your results to Adobe as well (bug submission form:  http://www.adobe.com/go/wish)

******BUG******

Concise problem statement:  Premiere CS6 crashes REPEATEDLY whenever I tweak drop shadow (and other times as well)

Steps to reproduce bug:

1. turn mpe on

2. add footage to timeline

3.  add drop shadow

4.  tweak quickly (click and drag paramaters) drop shadow

5.  Serious Error Premiere crashes

System specs:

Mac Pro OS Mountain Lion

Adobe Premiere (all updates)

2x3.46 ghz 6-core intel xeon

64gb of RAM

nvidea geforce gtx 570 open cl / cuda enabled

Very fast Raid 1400mb/s  R & W

[Kevin-Monahan]

Seastage wrote:

Just submitted my REPEATABLE crash to Adobe.  Can someone else try to emulate this crash on their mac?  If so please submit your results to Adobe as well (bug submission form:  http://www.adobe.com/go/wish)

Thanks so much for your submission.

[Kevin-Monahan]

genefama wrote:

Adobe admitted they were ignoring us and would keep doing so until we re-listed every complaint that we had already spent weeks listing in exhaustive detail--as if we were starting from scratch. Now you say quit complaining. Me, I just want to not have to re-link and re-render the same media everyday.

We aren't ignoring you. We are on the forums every day trying to help. Not sure what you're talking about there. I was the one who re-compiled the list of complaints (many of them not related to the OP's problem of "Serious Error", by the way) because the thread became so unruly, our staff was having a hard time following it.

If you are having trouble with relinking and rendering media, please create a separate post so we can work on that problem on its own.

Thanks!

[genefama]

Kevin Monahan wrote:

If you are having trouble with relinking and rendering media, please create a separate post so we can work on that problem on its own.

Thanks!

Hi Kevin,

I created a CS6 Takes my After Effects Comps Offline thread back in May.  Should I start it all over, making it less unruly?  😉

jk,

g

[Kevin-Monahan]

genefama wrote:

bossy, Not true, some progress was made.  We were accused of being whiners and conspiracy theorists!  ;-O

Never said anything about whiners, but those conspiracy theorists...tsk tsk!

[Kevin-Monahan]

bossy22 wrote:

I am really speechless, that

a) This hasn't been discovered during development. I mean, do they test the stuff they program?? This is happening to so  many people and there aren't that many configs on the mac platform. Not like windows and thats rock solid.

b) That they haven't figured anythingout yet.. The thread started in June, right??

unbelieveable...

bossy22,

a) Yes, we do test the program extensively. We had a beta program running for months before ship and bugs like this didn't appear. Yes, we had Mac users in the program. We also have internal QE, and other departments doing testing. When the app gets out in the wild, though, people have different installed software, configurations, and parts, so things can go awry.

b) As I remarked to ExactImage, software bug fixes are extremely hard to fix without repeatable steps. Fixing deeply rooted problems can't always be fixed quickly. As an editor, it is hard to understand why it takes a long time to make software bug fixes. Trust me, I've been there. It's definitely not an easy task.

Thanks!

[ExactImage]

Kevin,

Thanks for the feedback.

I do undertand the time it takes fix software - and the importance of getting repeatable steps - I was a software engineer for 20 years, and certianly liked the feedback I got from beta testers. 

I trust you know that there are a few additional people here willing to beta test your fixes prior to releasing it out in to the wild again

[Kevin-Monahan]

ExactImage wrote:

Kevin,

Thanks for the feedback.

I do undertand the time it takes fix software - and the importance of getting repeatable steps - I was a software engineer for 20 years, and certianly liked the feedback I got from beta testers. 

I trust you know that there are a few additional people here willing to beta test your fixes prior to releasing it out in to the wild again

Sure. As a former software guy, thanks for understanding our position. I know how frustrating waiting for a fix is.

Our beta program is only open prior to ship, so we'll have a new one opening soon for our next version. Don't worry, our engineers are going to test the heck out of this one.

[Kevin-Monahan]

ExactImage wrote:

C'mon Adobe, let's have a fix, or at least some indication that you are working on it and it 'will' be fixed in a 6.0.x update and not a 6.5.x release.  If it's not fixed in a 6.0.x update you will lose me (and I suspect many others) as a customer.  Period.  End of story. So, what's the score?

ExactImage, I've told you before that we know about many of these issues and are working on them right now. If a bug is repeatable, we can try for a fix, but if it is not repeatable, it is much more difficult.

When it comes to making software fixes, it takes time. This is really frustrating for users who need fixes right away. As an editor, I used to feel exactly the same way. Hang in there.

[lebucca]

My error is:

[/Volumes/BuildDisk/builds/tightykilt/shared/adobe/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283]

-Somebody said that I should verify my permissons, but that did nothing.-

[tinklevision256]

I am finding that on certain projects after a short while PP will just freeze, I then have to force quit, as it hangs when I try to close the program. When I try to shut down my computer, it also hangs, forcing me to do a Forced Shut down. I have re-installed Pemiere Pro 6, and also trashed all preferences, but the issue persists. I did notice that when I was going though the de-installation process, it asked me to quit out of Premiere pro + Dynamic Link manager, even though I had already forced quit out of the program.

I am certainly noticing issues are exaggerated when I am animating stills, often there will graphics glitches in exports containing stills. In general I am finding the system to be really unstable, in a way that I have never experiancd before (I have been using for over a year now from 5.0 onwards.)

I have a 12 Core 2.66 Mac running Mountain Lion.

[the_wine_snob]

I am certainly noticing issues are exaggerated when I am animating stills, often there will graphics glitches in exports containing stills.

For the issues with the Still Images, what are their general pixel x pixel dimensions?

Though CS 6 can handle larger Still Images, than some earlier versions, and can Scale better with MPE/CUDA, a bunch of extra pixels can strain systems, as there will be processing overhead used.

Good luck,

Hunt

[tinklevision256]

Hi Hunt.

Actually the job I am currently working on, features some Time Lapse Pro Res files at 5,184 x 3,456 in dimension. These were converted from the still image sequences using QuickTime 7. I have always done this (Export at full image size) since my Final Cut days, enabling me to be to animate and zoom into the image.

In dealing with stills in general, I have never found a document that stipulates what the ideal size/characteristics should be for Premiere Pro, when importing still images, then maybe I haven't looked hard enough.

Thanks for your response.