SUMO community discussions
adobe seems to be releasing version 11.3 of its plugin to the public http://get.adobe.com/flashplayer/
a user in the german forum is reporting about crashes after the update :-/
Sweet. Thanks for the update. Hmm guess I won't be grabbing that update then.
German forum? Link? Guessing you mean [support.mozilla.org/de/questions]? The forums really aren't separated by language, you can see all threads posted in any language thru the en-US forums.
Edit:
Ah! I knew you meant another site. Should of trusted my gut. :)
I've been to this site before but I couldn't remember its url. I also love its phpBB forums that are just like the MozillaZine forums.
Modified by NoahSUMO on
no, i meant the german community forum at http://www.camp-firefox.de/forum
edit: tried it & it was stable for me so far. this flash version seems to implement its own "plugin-conatiner", because content now seems to run in an own FlashPlayerPlugin_11_XXX.exe file & the firefox container sits idly by...
Modified by philipp on
here is one : https://support.mozilla.org/en-US/questions/929010
probably from Shockwave Flash 11.3 r300
Any issue in the Support Forum? Some people in the Italian forum reported a possible conflict between the sandboxed Flash and the Firefox plugin container.
One user solved disabling the sandbox
Like underpass said, problems with Flash 11.3 may due to the new Flash Player protected mode for Firefox, for example, see these threads on Adobe's forum:
Adobe's forum threads link to these instructions for a solution:
This solution was reported in the Firefox support forum, here: https://support.mozilla.org/questions/928820#answer-340016
Just for my curiosity: wasn't the beta version of the plugin tested with Firefox 12, 13, ESR?
Here's another forum thread, solved by disabling Flash 11.3 "protected mode":
underpass said
Just for my curiosity: wasn't the beta version of the plugin tested with Firefox 12, 13, ESR?
Even though Flash 11.3 beta is tested, it doesn't mean that all problems will be found. For example, I found Bug 759689 - Flash content is not loaded using Flash 11.3 Beta. It turned out that the issue only appeared on Windows 7 without the Service Pack, and it occurred in all Firefox versions tested. The bug did not occur on Windows 7 SP1 and I would guess that beta testers are more likely to have the latest OS updates.
I installed Flash 11.3.300.257 and, although it appeared to be working properly, I am having the same "silent crash" issue after closing Firefox 13 that was reported here:
I noticed it after looking in my %APPDATA%\Mozilla\Firefox\Crash Reports\Pending folder and finding two sets of .dmp and .extra files from today. I then went to about:crashes and submitted one of the two crash reports from today and got this report:
https://crash-stats.mozilla.com/report/index/a21db6b6-3bee-4d24-8fd2-8170b2120610 Firefox 13.0 Crash Report [@ LdrShutdownProcess ]
The related bug is Bug 747683 NEW Crash Report [@ LdrShutdownProcess ] with Flash 11.3 "Protected Mode for Firefox"
(I'm not planning on disabling protected mode since it's a security feature. I'll just vote for the bug, for now.)
Hey guys. We are investigating this as well. There are a couple of possible workarounds that I have posted in the Firefox 13 status thread. It would be awesome if we could get confirmation that the workarounds actually work.
@AliceWyman
Definitely understand your hesitation for disabling protected mode ;)
I did disable protected mode on my Windows 7 SP1 64-bit system as a test (I copied C:\Windows\SysWOW64\Macromed\Flash\mms.cfg to my desktop, opened in Notepad, added the line ProtectedMode=0 and, after first making a backup copy of the original file, deleted the original and dropped in my modified version to the Windows\SysWOW64\Macromed\Flash folder). That disabled protected mode and resolved my "silent crashes" (which also occurred in SeaMonkey 2.10) but I would rather keep the additional security that Firefox protected mode provides. Besides, having those files added to my Crash Reports\Pending folder, with the reports showing up in about:crashes, isn't a major issue for me.
Adobe's thread at http://forums.adobe.com/thread/1020038 has more info.
Modified by AliceWyman on
Everyone here seems to be referring to FF crashes caused by the 11.3 flash plugin upgrade. The other main problem people are having is it simply doesn't work at all. Alice referred to finding this in the 11.3 Beta in Windows 7 without SP1 where flash content wasn't loading. Well I have had SP 1 installed for months and that is not the fix, at least not with this supposed final release. The workaround is simple but nobody's mentioned the obvious. Roll back this "behaving like a beta" update to the previous 11.2.202.257 which still works perfectly. Just uninstall the plugin completely in Programs and Features and then click on any flash video content and then click on the message that FF needs to install an additional plugin (the message with the FF blue plugin icon, not the other flash player installation message below it) and FF should install the 11.2 version. Alice explained that this only works because the plugin finder service hasn't been updated yet (as of yesterday). If this doesn't work because the service has been updated, running a restore point should also restore the previous version. Or, you can click on the previous version 11.2.202.235 on FileHippo and be directed to Adobe's site but I tried the other way first, so can probably find it in Adobe's archives. Admittedly, Alice told me this is "not a good idea",but without saying why. I disagree, because it simply works and I'm having absolutely no problems since I did that - there's the proof. When there was that Norton Tool Bar compatibility problem caused by FF4.0 upgrade, we were also warned about not rolling back to the previous version until the Tool Bar issue got resolved. Norton was explaining that FF was no longer locking in the source code five months in advance so they had to wait for the final release to fix compatibility issues and then take weeks to test it. I simply rolled back the version number, got the Tool Bar back. I called Symantec and contacted the Developers and basically told them that although Mozilla was clearly responsible for this, since they were going to be rolling out new versions every six weeks,Symantec could not take weeks to test compatibility issues or they'll lose customers and that I couldn't understand why their Developers were not coordinating this with Mozilla's Developers. One week later, their Developers said they were doing exactly that and were pleased with the recent responses from Mozilla. That's the LAST TIME there was any delay with the Norton Tool Bar and Firefox upgrades. The FF Developers probably need to coordinate this flash plugin issue with Adobe's Developers. In the meantime, the workaround is really quite simple and it works with no problems and at least one other other user said that rolling back to the 11.2.202.257 version works also. And whatever security fixes there are in the new version, they're useless until the bugs are fixed.
CheckMate said
Or, you can click on the previous version 11.2.202.235 on FileHippo and be directed to Adobe's site but I tried the other way first, so can probably find it in Adobe's archives. Admittedly, Alice told me this is "not a good idea",but without saying why.
CheckMate, Rolling back to the previous Flash 11.2r202.235 plugin is not a good idea because it is insecure. Ref:
P.S. If Firefox crashes or freezes, or if Flash content won't play with the latest 11.3.300.257 update, I would say that the best workaround, short of a fix from Adobe, would be to temporarily switch to Google Chrome, which includes an integrated Flash plugin and also runs Flash in protected mode (ref). Next best IMHO would be to disable Flash Player's protected mode (mms.cfg edit)
Thanks Alice. These are the steps that we are planning on putting into a KB article to help with some deflection:
The realplayer download issue is through another variable in the mix, so best to rule that out. I spoke with Cheng yesterday and it seems that if IPC is off, it causes some instability as well. What do you think?
That as long as Adobe suggests to disable protected mode to work around the problem, I think the SUMO article should at least contain a link to that page.
@underpass
Agreed :) Working on the article right now. Verdi found an interesting fact. All of our existing flash articles have been getting horrible feedback in the last few days and it has impacted our overall article affectiveness score. Hopefully this will help!
Matt wrote this article: Flash 11.3 doesn't load video in Firefox and I linked to it from Flash Plugin - Keep it up to date and troubleshoot problems and Fix common audio and video issues.
I think that the "RealPlayer Browser Record plugin" phrase should be changed to "RealPlayer Browser Record Plugin extension" in the Flash 11.3 doesn't load video in Firefox article. It is an extension and writing plugin with lowercase suggests that it is a plugin.
