lots of "com.apple.helium-render-queue-exec-unit-gpu" crashes after update ... help?

After updating to FCP X 1.0.3, many older projects cause persistent crashes due to "com.apple.helium-render-queue-exec-unit-gpu". I suspect a third-party plug-in or else a less-than-failsafe project updating process (which happens automatically when 1.0.3 is launched and sees older projects for the first time). Since I can't even navigate to the project list, I can't try to fix these affected files. Sometimes Digital Rebellion's Quick Fix or resetting Compressor background rendering helps, but not consistently. Any suggestions (other than uninstalling all plugins etc.)?

Thanks!

Try manually deleting all project render files and event render files. Do this through the finder and not within fcpx. Then see if any of the projects you've done that to will open.

Yes, dgw is correct. I had this problem with one tiny demo Project yesterday.

I ended up having to do the following:
1- Manually delete render files.
2- Delete the CurrentProject.fcpproject file
3- Move the file from the Backups folder to where the CurrentProject.fcpproject file originally was.
4- Use Preference Manager to delete my FCP X preferences.

When I launched FCP X after that everything was fine.

I'm wondering whether ultimately a third-party plug-in is causing this. My prime suspects are Conduit at the top of the list and MBL 2 at number 2. Right now I've disabled Conduit, System seems more stable, but very sluggish once any MBL 2 is applied to h.264 encoded footage. FCP keeps swapping to drive, takes over a minute to shut down, drive keeps running another couple of minutes before things calm down. Once MBL 2 is applied in a session, it's always running in background, I think (application icon active in dock).

Yes, I did have to force quite MB, also. I forgot about that part. I've sent the MB folks an email that it's a problem. I've had MBL2 take for ever to render, freeze FCP X up, etc. I love it when it works, but have learned, after applying a look, quit FCP X right away, force quit MBL2, then relaunch. I had the problem again today. I've been loving MBL2 a lot, but it's big bugs are making me need to uninstall it until it's fixed. Sad day...

Good to know they're getting feedback on this from others as well. See here for another issue with MBL 2 that's driving me batty.

I believe that Red Giant released MBL2 for fcpx when fcpx was at version 10.0.2. Seems like after they did that Apple came out with 10.0.3 which may have introduced some incompatibilities. There are comments about this on Red Giants web site. My guess is that they will have a fix soon.....I hope.

No, it released for 10.0.3, as I purchased it with a limited time introductory discount price. They've had a blog going about it's development for FCP X, though before that.

Just got my confirmation email about my support case. I should hear something soon, will post and let you know what's going on.

Ditto here. I did manage to output one video graded within an inch of it's life by MBL2, with which I didn't have so many issues. I wonder whether the source codec may hove something to do with it? I'm having lots of "beachball" with h.264 footage, less with prores. The levels issue, however, is consistent.

It is not occurring with just MBL, I have gotten the same crash numerous time with FxFactory Pro Plug-ins as well as with Gen Arts Sapphire plug-ins

Yes, I've heard there is a lot of developer frustration with issues on the Apple side as well. Good to know. I finally got a response from RG that the problems I have written to them about are open and will at some point be addressed, but no word when. At the moment, I'm hanging in there with them, giving them the benefit of the doubt & crossing my fingers.

The render-cue crashes did seem to go away after deleting all the old version's render files; these don't seem to have been properly updated by 1.0.3. But I've also really reduced my use of 3rd party filters until things get sorted.