Public Health warning: 10.4.5 available if you dare!!!

[David Roth weiss]

After losing 5-days of my life to a faulty QT update, I’m going to heed your warning.

[John Calhoun]

yep. fcp5 and 10.4.4 has been very stable for me as well. I no longer seem to have to trash my preferences every day or the unexpected quitting. i might just hang here for a while.

pxlmvr

[Trinity Greer]

Ditto for me.

[David Darrow]

I have been using this as a guidline for system updates. I’ve never been crippled before but there’s no reason to risk it. Also, if I’m in the middle of a project with a tight deadline, I wait till that’s over (or the deadline relaxes) before doing any upgrades.

[Ernie Santella]

Thought I might pass along a little thing that just happened to me. I was getting crashes in FCP a little too often (Usually with long renders). Everything else ran and worked fine, except long renders.

It turned out that I had a bad RAM chip. I pulled pairs and test rendered until I found the bad chip. Then… ‘walla’ no crashes! I replaced it and life is all good again.

Also, what was weird was when I checked Apple system info, all the RAM was showing up. But, when rendering, I assume FCP would use most of the RAM and some info would hit the bad chip and crash the system.

Ernie Santella
Santella Film/Video Productions
http://www.santellaproductions.com

[Tony! Hulette]

[Ernie Santella] ”

Thought I might pass along a little thing that just happened to me. I was getting crashes in FCP a little too often (Usually with long renders). Everything else ran and worked fine, except long renders.

It turned out that I had a bad RAM chip. I pulled pairs and test rendered until I found the bad chip. Then… ‘walla’ no crashes! I replaced it and life is all good again.

Also, what was weird was when I checked Apple system info, all the RAM was showing up. But, when rendering, I assume FCP would use most of the RAM and some info would hit the bad chip and crash the system.”

Yep, bad memory is one of the hardest problems to diagnose with a Mac. You did a good job to find the problem. Apple’s hardware test can be used to check for memory problems as well. It should be on one of your OS X disks that came with your Mac. Its not perfect however, and doesn’t always identify bad memory. I always recommend using name brand memory (especially from Crucial.com) and only install same size memory sticks, all purchased at the same time. Especially, if you are using your machine for heavy production where reliability critical.

Tony!

[Tony! Hulette]

[dthree] ”

I have been using this as a guidline for system updates. I’ve never been crippled before but there’s no reason to risk it. Also, if I’m in the middle of a project with a tight deadline, I wait till that’s over (or the deadline relaxes) before doing any upgrades.”

The way we setup our systems (and systems for others), is to install two identical internal hard drives. We clone the startup drive to the second drive (backup). Before doing any updates, we update the clone. That way, if we do encounter a problem with the new update, we can simply restore our working system from the backup drive. Or, if we are in a big rush we can simply startup off of the backup drive and continue working. After installing a new update, that appears to be working, we don’t clone over our backup drive for at least a week or two (sometimes longer) until we are sure that the new updated drive it working correctly and is stable.

Of course, always repair your drive and permissions before, and after, any major updates and/or backups.

Tony!