IPhoto unexpectedly quits when viewing or editing certain photos

Question

I have just returned from three weeks abroad and had hoped this issue would have been handled by Apple in the interim, but the same status message is still on their web site as when I left.
"After updating to QuickTime 7.1.3, iPhoto may unexpectedly quit while attempting to import or edit certain photos."
They offer several workarounds, which don't seem to work, and/or are impractical given the huge numbers of photos that are affected in my library, and/or entail losing all the metadata I have so carefully developed.
We're not talking a library of 200 pix of Aunt Edna at the beach. Much of my 10,000 image library consists of professional and technical work that I must deal with on an almost daily basis. Has anyone else, who has experienced this problem found a solution? This is big!
I have library backups, but am wondering if they are also affected and/or if they will be corrupted once I bring them back to the computer with the new Quicktime version, since I don't understand the mechanism of the problem.
OldToad offers a bit of software that embeds RGB profiles and suggested using it. That didn't seem to be the answer, however.
Help!

Answer 1

As an add on to your post I've written an Applescript that will batch embed the sRGB color profile in folders of image files. If the user has a lot of files to process this can shorten the process time a lot. The script, Embed sRGB Colro Profile can be downloaded from Toad's Cellar.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.