How do I work out which plugin is causing the problem?
I had FF freeze up (it 'usually' will unfreeze after several minutes). I cancelled FF which had stopped responding and then mentioned plugin container problem, but not which plugin! I expect it was SWF file. Help- TB gives 43,635 so truncated it to < 30K. Anyway, both cancelled details follow:
==
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangXProcB1 Application Name: firefox.exe Application Version: 1.9.2.3909 Application Timestamp: 4c8fdcc5 Hang Signature: 6115 Hang Type: 6208 Waiting on Application Name: plugin-container.exe Waiting on Application Version: 1.9.2.3909 OS Version: 6.0.6002.2.2.0.256.6 Locale ID: 5129 Additional Hang Signature 1: e0b10083acdc710079bef600302ae36f Additional Hang Signature 2: 3a0b Additional Hang Signature 3: 0de7a3cb351bf80645d8c65fc5931f2e Additional Hang Signature 4: 6115 Additional Hang Signature 5: e0b10083acdc710079bef600302ae36f Additional Hang Signature 6: 3a0b Additional Hang Signature 7: 0de7a3cb351bf80645d8c65fc5931f2e
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
====
Problem signature:
Problem Event Name: APPCRASH Application Name: plugin-container.exe Application Version: 1.9.2.3909 Application Timestamp: 4c8fdc89 Fault Module Name: ntdll.dll Fault Module Version: 6.0.6002.18005 Fault Module Timestamp: 49e03821 Exception Code: c0000005 Exception Offset: 00048b02 OS Version: 6.0.6002.2.2.0.256.6 Locale ID: 5129 Additional Information 1: ca4b Additional Information 2: 0db6cc4f646c2246ddf8a462e3add7af Additional Information 3: 5f3c Additional Information 4: bbd63bd772831dab31cdc8164e6f07a1
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
Всички отговори (10)
You can try disabling the plugins to find the culprit. For details on the process see Troubleshoot issues with plugins like Flash or Java to fix common Firefox problems.
Thanks for that. Looks like it was Shockwave Flash 10.1.85.3, although I didn't get exactly the same error. It sure would make things easier if Plugin Container maybe kept track of its stack &/or displayed which plugin was active. The actual crash looks like it was in NTDLL.dll!RtlEnterCriticalSection@48af0. Where do we go from here? Is this just part of the other SWF issues or 'something else'? Maybe it would be good if PluginContainer did do a stack trace. Is there a debug version that does that?
See http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins
Your above posted system details show outdated plugin(s) with known security and stability risks.
- Java Plug-in 1.6.0_13 for Netscape Navigator (DLL Helper)
Update the Java plugin to the latest version.
- http://java.sun.com/javase/downloads/index.jsp (Java Platform: Download JRE)
oh dear. When I run FF - Tools - Addons - Plugins - Find Updates it tells me that both of the Java Platform 1.6.0.13 are up-to-date. Maybe the FF dev team (or whoever handles the up-to-date process) should be informed about the up-to-date processing error. Maybe it's the same with the Shockwave Flash check too.
Okay, I've upgraded Java and managed to reproduce identical problem (well, plugin-container.exe, NTDLL Exception Code: c0000005, Exception Offset: 00048b02). I will post as new support issue as TS Info will have changed
hmmm. The new support issue has been frozen (as a duplicate) so I guess that this issue is the one that people need to look at. If people read my previous post, they may think that this isn't active! So ... I'll post this to say that the problem is still there, and I have received no indication that any progress has been made. Is there anything I can do, or supply anyone with, to help progress this issue along to a fix?
Did you submit crash reports in Firefox?
What you posted above is an MS error report and doesn't give any information.
See:
- http://kb.mozillazine.org/Firefox_crashes
- Troubleshoot Firefox crashes (closing or quitting unexpectedly)
If you have submitted Breakpad crash reports then post the IDs of one or more Breakpad crash reports (bp-xxxxxxxx-xxxxxxxxx-xxxx-xxxxxxxxxxxx).
You can find the IDs of the submitted crash reports on the about:crashes page.
You can open the about:crashes page via the location bar, just like you open a website.
See: http://kb.mozillazine.org/Breakpad (Mozilla Crash Reporter) and [[Mozilla Crash Reporter|Mozilla Crash Reporter:Breakpad]]
You posted this in your other topic (which was locked as a duplicate of this topic ):
When playing a swf video, and clicking on 'sub-video' from swf menu, FF will often freeze for extended periods. When I End Task from Task Manager, after FF has been ended, it then mentions 'Plugin Container for Firefox has stopped working' but Fault Module Name is NTDLL.
You also posted a similar issue here: http://support.mozilla.com/en-US/questions/754708 Firefox is freezing for extended periods
Have you tried disabling the Firefox "crash protection" feature that uses plugin-container.exe? See Plugin-container and out-of-process plugins (MozillaZine KB) for details.
Променено на от AliceWyman
The MS report tells me that it crashed in function RtlEnterCriticalSection in NTDLL.dll, which was called from plugin-container.exe. I have submitted a couple of crashes (which is all there are in past month, which surprises me, as I have had to 'force closed' Firefox way more times than that). They had not been sent due to 'throttling' but . I don't even know if these now-bp reports relate to the problem; one seems to be more about SWF than the plugin-container, but still, hopefully they'll be useful for something. bp-823403e2-f6ed-4ff2-ad00-59e912101012 2010-10-09 17:24 bp-f035f836-4dd6-4ec7-be50-ce3d62101012 2010-10-09 17:24
I've set all dom.ipc.plugins.enabled.* to false and things are starting to behave better. Could it be that now the various plugins run in the same thread, and so drop straight through the EnterCriticalSection (even if the locked object wasn't released like it should be), but when the plugins use the plugin-container, the CriticalSection object is locked by one thread and so will block another plugin-container thread when it tries to do its own EnterCriticalSection with the same object? Just a thought.