Ok, I think I was receiving the error because my OS and APPs drive had only 12MBs of free space!  (A friend installed a huge game on the drive without telling me.)

Now that my drive has lots of free space again, the error does not seem to be appearing.

[/Volumes/BuildDisk/builds/tightykilt/PremierePro/UIFramework/Make/Mac /../../Src/TimeBarControl.cpp-170]

The latest cause for lock up. This is really becoming a problem for me.

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.

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.

I have gotten many Serious Error's as well.  Here is a list of how I get those errors:

1) Creating Metadata in Project Bin - When I am adding comments/descriptions to a clip, if I happen to scroll via my mouse, PP crashes and I get the Serious Error message.

2) Loading a RED/ProRes project with about 15,000 clips - Sometimes Premiere will crash while trying to load the Media.  This is my Master Project consisting of clips from 5 filmers.  It will load fine sometimes, but crashes about half the time.  A trend I've noticed is if I'm using a different program while PP is trying to load media.

3) Project Managing clips - While trying to create a Trimmed project with RED files, Premiere will give me the error message after analyzing the project and when it begins trimming.  Copying files to new location seems to work fine.

4) While trying to link media - In some cases, when I'm trying to link media that is offline (specially .R3D files), I will get the error message.

Myself and my other editors have all been getting these issues, on different machines.  It is getting to the point where it is very tough to accomplish edits when even loading the project will crash PP.  We all get other errors and crashes that don't give us the "Serious Error" message, but I'll save those for a different thread.

My specs are:

Mac Pro

OSX 10.6.8

11GB RAM

NVIDIA GeForce 7300 GT

I am running on an older machine that doesn't support CUDA and am running MPE via software only.  I haven't been getting as many "playback" bugs as other users here.

It looks like we are all hoping for more updates as soon as they are available.  I would much rather be updating PP every week and hope for fixes rather then continue working with all bugs/crashes for another "X" amount of time.  Can anyone give us a timetable for when the next update will be available?

Thanks.  This discussion has been very informative.

v6.0.2 - I just got a Serious Error dialog while keywording.  

Rebooted & wait for everrything to load.  Tap the space bar by mistake, Pr takes off playing audio with no video movement, the mouse moves but I can't click on anything.  The keyboard no longer responds and the mouse moves but won't click.  Have to force power off using the power button.

Reboot - everything works normally.

< sigh >

We do get the occasional glitch from premiere pro on the windows 7 systems but nothing like we're getting on the Mac, yet Adobe software is the only one crashing on the Mac, whereas everything else seems solid. 

Good news for me. I decidied to re-install entire system from scratch. This has (for now at least) made my system stable. Crashes have reduced considerably. I still get the serious error every so often, but I can live with it.

Additionally, when this happens it looses connection with all preview files, so I have to re-render the entire sequence.

OK...I spoke too soon...more than a dozen serious error crashes today....all while I was screening a clip in the project through the browser by double clicking it then playing to select in and out points...this is a consistent cause that has happened a dozen times today.

I submitted a bug report, trashed preferences/restarted/used house cleaner in Digital Rebellion Pro Maintenance Tools...restarted, searched for corrupt clips and found that all of my clips were on the corrupt clip list...so what value is that?

This is a 1080/60i timeline with mostly XDCAM EX clips 1080/60i, a 4 or 5 1080/30P clips from a canon 5D and a couple of gopro 1080/30p clips.  I exported all stills to video, exported the upressed shots to a single video track and don't know what else to try.

I was going along pretty smoothly until this update, so now I guess I'm paying...

I guess I just had to vent a little with I'm sure no help to fix this issue until the geniuses at Adobe can appy themselves to solving these an many other problems.  Perhaps they should be working on Premier Pro instead of the "Adobe Anywhere" project.  Maybe in the cloud on their super-duper servers there won't be any problems with "serious error".  Right! and if you believe that, I have a little piece of swamp land on Mars to sell.

thx...jw

Coincidentally right before I shut down this afternoon I made a new sequence to finish the last 8 minutes of the show, but didn't have a chance to do much.  I'm shooting for the next 10 days so won't have a chance to try the fix for awhile.

Since my crashes were occurring just viewing clips from the browser or project, I wasn't convinced the sequence was the culprit, but will definitely give it a try.

I'll let you know in a couple of weeks how it went and thanks very much for the suggestion.

Jim Watt

I finally got the chicken out of me, after reading so much about the serious error thing, and decided we needed to do a real edit in CS6. Have used 5.5 with no real issues. This morning, only a few days into an edit I recieved the serious error message and crash. Granted I was on 6.0.1 and had not on the latest CUDA update. So now I'm up to the latest, 6.0.2 and CUDA 5.0.24 and will see how it goes. We are trying this on our mobile edit system first (MacBook Pro, 17", 4 core i7, 16 gigs ram, Lion 10.7.4, 4 drive eSATA RAID using the GPU exceleration. Footage is mostly HDV/Mpeg2 with some H.264.

Before the first crash Premiere seemed much more sluggish on the timeline than the same footage in 5.5 on the same system. After hours of editing the only way to get things to play smoothly on the timeline (even when rendered) was to close Premiere and then reopen. Wow, I'm not yet feeling the love, but I do like the interface so much more than 5.5.

I am finding that every time I have a "Serious Error" message, and then open recovery project, it always looses contact with all preview files, so I have to keep re-rendering. Anyone else get ths as well?

There is no doubt that MPE is the cause (for me at least) of most of the issues. Is this somthing to do with Moutnain Lion?

Its a right pain. I am using MXF files from the canon C300, wondering if this is part of my issue at least. I have spoken to customer support a few times now, and they don't seem to be able to offer a solution.

I get the black screen a lot. In general, once I start to get a sequence of serious errors, the only solution is to cold boot the computer. I noticed a while back when I was re-installing the software, that the de-install plug-in would not continue until I quit out of Premiere, which I had already closed out of.

I spoke with techinical support yesterday,who told me that a forthcoming update is going to solve the problem. Adobe recognize that there is a problem with Nvidea-Cuda drivers, especially on the the higher end cards. Fingers crossed.

Glitchdog wrote:

 

I decided to turn off the OpenCL/GPU acceleration on the MacBook Pro before I saw your post and it was amazing

Not really amazing to me since CUDA is what is advertised to work.  Having to disable it makes it worthless.  It's as if MPE really stands for Mercury Playback EXPERIMENT!

I have to say, despite this recent round of problems, I so much prefer Premiere to FCP, the thought of going back makes me shiver. Key Frames yes! aside form the Cuda fix, all I need is the addition of Pixel motion function and the ability to add Warp Stabilizer to different frame sizes in a sequence, and I will be golden!