User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 Build ID: 20121119183901 Steps to reproduce: Installed Flash plugin version 11.5 (or any 11.x) Start FF 17 Go to any site with flash content (like youtube.com) Actual results: Browser hang. Expected results: Browser must work correct Workaround: I can install Flash plugin 10.3, and than browser works with Flash "correct", but some sites tell about outdated flash plugin
doesn't block development.. Have you already tried the Firefox safemode ? http://support.mozilla.org/en-US/kb/Safe+Mode
Yes, I have tried to start FF in Safe Mode. FF hangs on sites with flash content. Even if I kill plugin_container.exe, FF does not resume work.
could be something special with Windows Server2012
Do you see the plugin crashed UI after hanging for 45 sec? Can this be reproduced on Nightly or Aurora? If so, the hr-... ID for one of those hangs from about:crashes would be informative.
This issue reproduces on FF 17/18/19/20. But only on interactive logon. When I log on to Windows 2012 Server via remote desktop, even FF 17 works fine.
And also, about:crashes does not contains data about crash (i killed ff via process manager)
Today I have installed latest flash 11.5. Now flash plugin crashes with attached message. I have send crash report 41228869-6a48-487a-93c5-2916ab5ba11c
Is "41228869-6a48-487a-93c5-2916ab5ba11c" from about:crashes ? In that case click on it once to send the report. The ID should change to something with a bp- in front.
Is the same flash plugin working with other browsers like Opera or Chrome ? Note: IE is using a different plugin (activeX plugin) The hang is probably related to bug 797116
Opera with flash plugin 11.5 works as expected
Could you try this with a nightly build? http://nightly.mozilla.org/ this will give me a better hang report to help diagnose the issue.
This is interesting, and probably not related to bug 797116. In the browser process we are creating the plugin @ nsNPAPIPlugin::CreatePlugin. Something in that method fails, and we end up releasing the nsNPAPIPlugin at the end of the function. So either CreatePlugin failed *before* it called NP_Initialize, or NP_Initialize itself failed. This means the Flash plugin is nonfunctional in some way that we can't tell from the stack. So fixing this bug is unfortunately not going to make the Flash plugin actually work. The nsNPAPIPlugin destructor calls into mozilla::plugins::PluginModuleParent::~PluginModuleParent which as a fallback calls into mozilla::plugins::PPluginModuleParent::NP_Shutdown which always calls NP_Shutdown via IPC even if NP_Initialize was never completed. I don't remember why I added that fallback originally, but I'm think it's a bad idea and we should just terminate the child.
Created attachment 686234 [details] [diff] [review] Just Close() the channel, rev. 1
Other workaround — turn off Flash Protected Mode http://techdows.com/2012/06/disable-flash-players-protected-mode-for-firefox.html
The hang part of this got fixed along the way. Not sure that Windows 2012 server actually works or whether Flash continues to crash, but that's a different bug.