So do you still have the issue or not?
And btw, the actual problem is that there is a broken symlink in the QuickTime framework folder, which causes all the problems. Fix the symlink, and tada! the problems go away until the actual cause, whatever it is, does whatever it does again to break the symlink.
I am not currently experiencing the problem on either my internal drive, on which Securtiy Update 2013-003 was never installed, nor on my external drive, since August 18, when I reinstalled 10.8, updated to 10.8.4, but did not install the Security update.
With respect to the cause of the problem and its relationship to the security update, I agree that something is braking the symlinks in the QuickTime framework folder.
As I mentioned in my message of Aug 4, I looked in /System/Library/Frameworks/QuickTime.framework/ on my external drive and found broken symlinks.
The security update puts files and valid symlinks in the QuickTime framework folder, but in a matter of hours or days, those links are broken. Without the security update installed, the required symlinks do not break. I certainly do not know why.
Looking back at this morass of a thread, I see that you have a Symantec security product installed. There's no way that's ever going to do anything for you but cause problems. I don't know whether it's causing this problem, but even if it isn't, you should get rid of it according to the developer's instructions.
Unlikely to be Symantec as I don't have that installed and have had this issue as well. Interestingly enough, I have Sophos for Mac running on all three of my Macs so it's also unlikely to be that. The only one that seems to be affected by the Security Update is my ancient (mid-2007) iMac. My other two Retina MacBooks took the security update just fine. On my iMac, I have not installed the Security Update and have been running with no issues for about a month or so. I have no idea what's breaking the symlinks but I still think this is an Apple issue to resolve. Hopefully Mavericks will fix the issue.
I have Symantec running on both of my iMacs. Only my 24" iMac has the problem. I installed Symantec when I had a Quicken crash. The Quicken support page said that it was not Quicken's fault and that I should check for a virus. So I installed symantec and scanned my disk. Symantec reported a virus in a document that I know had no such thing. In any case the reported virus was a Windows virus.
I checked the modifiied date on the Symantec files. It shows Jul 18, 2013, which is just two days before I started this thread on QuickTime crashes. It may just be a coincidence, but I cannot rule out the possibility that Symantec is the cause. I will uninstall it.
I have now unistalled Symantec from external drive, and restarted. This is the only drive on which it was installed.
I then installed Security Update 2013-003 on that drive and restarted. A check with Software Update shows all software is up to date.
I will use that drive for a while and see if the problem recurrs. I will report my system status in a few days.
The problem may lie in QTKit.framework. I used "ditto" to restore a backup copy of QuickTime.framework but that did not work. So i also restored QTKit.framework and was able to use QuickTime Player again.
Here are the steps if you are familiar with using Terminal and sudo.
First make a backup copy of QTKit.framework and QuickTime.framework AFTER you have confirmed that QuickTime Player is working.
1. Create a directory to hold the backup of the frameworks
sudo mkdir -p /System/Library/Frameworks.BACKUP
2. Backup the frameworks
sudo ditto /System/Library/Frameworks/QTKit.framework /System/Library/Frameworks.BACKUP/QTKit.framework
sudo ditto /System/Library/Frameworks/QuickTime.framework /System/Library/Frameworks.BACKUP/QuickTime.framework
Now whenever QuickTime Player crashes on launch, you just need to run the following commands to restore the frameworks.
1. Move the existing frameworks aside
sudo mv /System/Library/Frameworks/QTKit.framework /System/Library/Frameworks/QTKit.framework.BAD
sudo mv /System/Library/Frameworks/QuickTime.framework /System/Library/Frameworks/QuickTime.framework.BAD
2. Restore from the backup copy of the frameworks
sudo ditto /System/Library/Frameworks.BACKUP/QTKit.framework /System/Library/Frameworks/QTKit.framework
sudo ditto /System/Library/Frameworks.BACKUP/QuickTime.framework /System/Library/Frameworks/QuickTime.framework
3. Launch QuickTime Player to verify it is working.
I will do the backup tonight so I have it. This is great, thank you.
Getting closer to the cause. We are hovering around it but can't seem to nail it down. For what it's worth, I am running Sophos (never had a problem with it at all), not Symantec, and I was having the problem but no more since complete clean reinstall 10.8.4 with the security update, Sophos and without Skype.
Apple just released 10.8.5, doesn't mention fixing our problem. There are probably Security fixes in this as Apple also released Separate Security updates for earlier OSes.
10.8.5 Combo update is probably your best option.
Oh goody. I'm really hoping this fixes the problem.
I read through the support document, and these are the changes made for QuickTime:
Available for: Mac OS X 10.6.8, Mac OS X Server 10.6.8, OS X Lion v10.7.5, OS X Lion Server v10.7.5, OS X Mountain Lion v10.8 to v10.8.4
Impact: Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution
Description: A memory corruption issue existed in the handling of 'idsc' atoms in QuickTime movie files. This issue was addressed through additional bounds checking.
CVE-2013-1032 : Jason Kratzer working with iDefense VCP
It doesn't mention anything about our problem, but it may fix it.... Here's hoping.