Hi, The crash report link you provided was definitely a known issue in the beta, but we believe it's resolved at this point. Firefox saves all of your crash logs, so if you were running the beta, that may be what you're seeing. It's also possible that our fix isn't 100% effective -- it's timing-related and really hard to reproduce -- but you can see a drastic reduction in the incidence of the crash (the Mozilla folks point this out as well) in the statistics. The release version of Flash Player 11.3 contains a fix for this crash. I'm not able to reproduce the issue on my end using Firefox 13 and Flash Player 11.3.300.257 at this point. I'll leave my stress-testing suite running over the weekend to see if I can catch anything, though. If you happen to run across steps that consistently cause a crash (it might be specific to doing those things while visiting specific content), that would be super helpful. Anyway, by making those mms.cfg modifications, you've disabled Protected Mode. If you're interested in the implementation and why you see a difference in processes displayed, there's a good write-up here: http://blogs.adobe.com/asset/2012/06/inside-flash-player-protected-mode-for-firefox.html To get the crash dumps -- which are what we feed to the debugger, do the following: If you look under C:\Users\<you>\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending\ Just grab anything from today. If you submitted them already, they'll be copied to \submitted\ instead. If you're not finding the AppData directory, it's because it's hidden. Do the following to make them visible. You can zip that stuff up, or just attach the files to the bug one at a time. Either way is fine. From Windows Explorer Click Organize > Folder and Search Options Click the View tab Under Hidden Files and Folders, click Show hidden files, folders or drives Uncheck Hide protected operating system files and acknowledge the warning. Thanks!
... View more