X
Tap here to go to the mobile version of the site.

منتدى الدعم

HELP NEEDED. Plugin container stopped working / Script does not respond

Posted

Hi! I am aware that there are numerous articles about this problem, but unfortunately none of them solves my problem.

Very frequently, at least once a day (usually from 3 to even 7 times a day) my Mozilla Firefox freezes and I am forced to restart it. It typically occurs when I try to open a page with some interactive content in it (youtube, some fancy flash pages, even gmail document preview). When I try to close it, Windows pops up a message saying that "Firefox stopped working" and terminates the application itself, and then another window pops up, saying "Plugin Container for Firefox stopped working". It's usually either that, but sometimes Mozilla also shuts itself without any warning and the same message appears.

As for "script does not respond", it does happen as well, although way more seldom. Usually it happens on the pages with lots of images. The whole browser then freezes for couple of seconds, then it pops up a window saying that the script does not respond and asks whether I want to force it to continue or not. It doesn't make any difference which option I choose because usually the browser crashes anyway.

I am using version 34 and I made sure all my plugins and addons are up to date. I also disabled hardware acceleration and tried to reinstall whole flash thing. I wonder whether it's the fault of one of my addons, but I admit I am not too eager to try and disable them all and then test it one by one because it would take up way too much time. Apart from that, none of the previous solutions seem to help, and the problem really gets on my nerves because numerous times I lost a huge block of text I was writing. Now I learned to copy everything I write couple of times :/

Maybe the crash reports will help. I'll link them from the newest to the oldest (for some weird reason they are 3 crash reports from today, yesterday and 3 days ago - weird, because the browser has shut itself today at least twice, not to mention previous days):

https://crash-stats.mozilla.com/report/index/ba7f5087-3d7d-4b2c-b9b1-04e6d2150105 https://crash-stats.mozilla.com/report/index/72eaf792-5f06-445b-806c-cd7922150104 https://crash-stats.mozilla.com/report/index/c3f81ff8-df10-45a6-8400-1c5912150103

I'll be glad for any help because, honestly, I can't stand it anymore. No reinstalling of Firefox or restoring settings to default have helped me yet.

Hi! I am aware that there are numerous articles about this problem, but unfortunately none of them solves my problem. Very frequently, at least once a day (usually from 3 to even 7 times a day) my Mozilla Firefox freezes and I am forced to restart it. It typically occurs when I try to open a page with some interactive content in it (youtube, some fancy flash pages, even gmail document preview). When I try to close it, Windows pops up a message saying that "Firefox stopped working" and terminates the application itself, and then another window pops up, saying "Plugin Container for Firefox stopped working". It's usually either that, but sometimes Mozilla also shuts itself without any warning and the same message appears. As for "script does not respond", it does happen as well, although way more seldom. Usually it happens on the pages with lots of images. The whole browser then freezes for couple of seconds, then it pops up a window saying that the script does not respond and asks whether I want to force it to continue or not. It doesn't make any difference which option I choose because usually the browser crashes anyway. I am using version 34 and I made sure all my plugins and addons are up to date. I also disabled hardware acceleration and tried to reinstall whole flash thing. I wonder whether it's the fault of one of my addons, but I admit I am not too eager to try and disable them all and then test it one by one because it would take up way too much time. Apart from that, none of the previous solutions seem to help, and the problem really gets on my nerves because numerous times I lost a huge block of text I was writing. Now I learned to copy everything I write couple of times :/ Maybe the crash reports will help. I'll link them from the newest to the oldest (for some weird reason they are 3 crash reports from today, yesterday and 3 days ago - weird, because the browser has shut itself today at least twice, not to mention previous days): https://crash-stats.mozilla.com/report/index/ba7f5087-3d7d-4b2c-b9b1-04e6d2150105 https://crash-stats.mozilla.com/report/index/72eaf792-5f06-445b-806c-cd7922150104 https://crash-stats.mozilla.com/report/index/c3f81ff8-df10-45a6-8400-1c5912150103 I'll be glad for any help because, honestly, I can't stand it anymore. No reinstalling of Firefox or restoring settings to default have helped me yet.

Chosen solution

The crash report refers to two components -- ad2mpegin.dll and ad2mpgdmux.dll -- as the last bits of software Firefox (or the active plugin) was running. Based on some web searching, these are codec files installed by Adobe Premiere (or Premiere Elements) supplied by MainConcept AG in its decoder pack.

(I couldn't find these DLLs on a system with Adobe Premiere Elements 10 so that might be an incomplete installation or these files might no longer be used. Web references mention Premiere Elements 2-7.)

One possible issue is that the codec files need to be updated, another is that they are corrupted, and a third is that Firefox simply is not compatible with any version of them.

Because there are many malware-laden codec packages on the web, I would be hesitant to install updates from an unofficial source if neither Adobe nor MainConcept can help. Instead, I would research a way to bypass these files by having Windows use its own built-in media features instead. (Time doesn't permit me to search for how to do that this morning.)

Read this answer in context 2

Additional System Details

Installed Plug-ins

  • Wacom Dynamic Link Library
  • Adobe PDF Plug-In For Firefox and Netscape 10.1.12
  • Gadu-Gadu Plug-in
  • GEPlugin
  • Google Update
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Next Generation Java Plug-in 10.71.2 for Mozilla browsers
  • Office Live Update v1.5
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Shockwave Flash 16.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.1.5.155
  • 5.1.30514.0
  • VLC media player Web Plugin 2.1.3
  • Plugin for Wacom tablets.
  • NPWLPG
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
  • iTunes Detector Plug-in

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Firefox/34.0

More Information

jscher2000
  • Top 10 Contributor
8758 solutions 71665 answers

Hmm, that's pretty bad. Often if Windows is stepping in with the crash report, then the issue is with a driver incompatibility, most commonly a display driver.

Here are a couple things to try:

(1) Disable Firefox from using hardware acceleration

This is the traditional workaround. You can use:

"3-bar" menu button (or Tools menu) > Options > Advanced

On the "General" mini-tab, uncheck the box for "Use hardware acceleration when available"

That takes effect the next time you exit and start Firefox up again, which the way you describe it, might be quite soon.

(2) Disable the Flash player plugin from using hardware acceleration

This is a separate setting. See this support article from Adobe: http://helpx.adobe.com/flash-player/kb/video-playback-issues.html#main_Solve_video_playback_issues

(3) Disable the Flash plugin's protected mode feature

Protected mode has security benefits, but is not compatible with all systems for some reason. It can stall scripts on some systems, for example. You can disable the feature by creating or editing a settings file. The following pages/posts provide different approaches:

Any improvement?

Hmm, that's pretty bad. Often if Windows is stepping in with the crash report, then the issue is with a driver incompatibility, most commonly a display driver. Here are a couple things to try: (1) Disable Firefox from using hardware acceleration This is the traditional workaround. You can use: "3-bar" menu button (or Tools menu) > Options > Advanced On the "General" mini-tab, uncheck the box for "Use hardware acceleration when available" That takes effect the next time you exit and start Firefox up again, which the way you describe it, might be quite soon. (2) Disable the Flash player plugin from using hardware acceleration This is a separate setting. See this support article from Adobe: http://helpx.adobe.com/flash-player/kb/video-playback-issues.html#main_Solve_video_playback_issues (3) Disable the Flash plugin's protected mode feature Protected mode has security benefits, but is not compatible with all systems for some reason. It can stall scripts on some systems, for example. You can disable the feature by creating or editing a settings file. The following pages/posts provide different approaches: * Adobe support article under the heading "Last Resort": [http://forums.adobe.com/message/4468493#TemporaryWorkaround Adobe Forums: How do I troubleshoot Flash Player's protected mode for Firefox?] * Manual steps: https://support.mozilla.org/questions/968190?page=5#answer-509209 * Batch file to automate the manual steps: https://support.mozilla.org/questions/982093#answer-518078 (alternate version of Carm's batch file with a few changes by me: [https://onedrive.live.com/?cid=f7d304d92388737d&id=F7D304D92388737D!336&ithint=file,.bat&authkey=!AP2FXW2Y_3BXZyo]) Any improvement?
jscher2000
  • Top 10 Contributor
8758 solutions 71665 answers

Also, thank you for the crash reports. Generally speaking, if Windows is displaying the crash dialog instead of the Mozilla Crash Reporter coming up, it indicates that Firefox didn't record specific data on that crash. There may or may not be anything useful in the Windows event logs; whatever is there generally is difficult to interpret (at least for me).

Also, thank you for the crash reports. Generally speaking, if Windows is displaying the crash dialog instead of the Mozilla Crash Reporter coming up, it indicates that Firefox didn't record specific data on that crash. There may or may not be anything useful in the Windows event logs; whatever is there generally is difficult to interpret (at least for me).
jscher2000
  • Top 10 Contributor
8758 solutions 71665 answers

The crash reports refer to some Symantec/Norton security software components being called in other threads, so you might want to make sure that software is as up-to-date as possible (sometimes LiveUpdate needs to be run multiple times) in case an incompatibility there is an issue.

The crash reports refer to some Symantec/Norton security software components being called in other threads, so you might want to make sure that software is as up-to-date as possible (sometimes LiveUpdate needs to be run multiple times) in case an incompatibility there is an issue.

Helpful Reply

Hello jscher2000,

thank you very much for your replies and help. As I've written, I have already disabled hardware acceleration in Flash before, but I've followed your other instructions and disabled it in Firefox as well. I also tried disabling Flash safe mode and I discovered that I have disabled it some time ago already (the line was already added to .cfg file), yet it didn't help, apparently. Last but not least, I've checked the version of my Norton - it is up to date.

I'll see how the browser behaves after disabling hardware acceleration in the options. If the problem still occurs, I'll update the topic.

Hello jscher2000, thank you very much for your replies and help. As I've written, I have already disabled hardware acceleration in Flash before, but I've followed your other instructions and disabled it in Firefox as well. I also tried disabling Flash safe mode and I discovered that I have disabled it some time ago already (the line was already added to .cfg file), yet it didn't help, apparently. Last but not least, I've checked the version of my Norton - it is up to date. I'll see how the browser behaves after disabling hardware acceleration in the options. If the problem still occurs, I'll update the topic.

Question owner

So far so good. No crashes today, but the browser froze one time (and then it unfroze after a couple of seconds, so I guess it's more or less good). I'll keep testing it!

So far so good. No crashes today, but the browser froze one time (and then it unfroze after a couple of seconds, so I guess it's more or less good). I'll keep testing it!

Helpful Reply

Aaand it's gone. Just a minute or two ago firefox closed itself (upon entering some tumblr page) and again - there was a pop up window saying 'Plugin container for Firefox stopped working' BUT this time the regular Mozilla crash report window popped up as well (instead of the Windows one). I'll link the crash report.

https://crash-stats.mozilla.com/report/index/f8e9b5cf-1b26-4110-ba34-a899d2150107

Aaand it's gone. Just a minute or two ago firefox closed itself (upon entering some tumblr page) and again - there was a pop up window saying 'Plugin container for Firefox stopped working' BUT this time the regular Mozilla crash report window popped up as well (instead of the Windows one). I'll link the crash report. https://crash-stats.mozilla.com/report/index/f8e9b5cf-1b26-4110-ba34-a899d2150107
jscher2000
  • Top 10 Contributor
8758 solutions 71665 answers

Chosen Solution

The crash report refers to two components -- ad2mpegin.dll and ad2mpgdmux.dll -- as the last bits of software Firefox (or the active plugin) was running. Based on some web searching, these are codec files installed by Adobe Premiere (or Premiere Elements) supplied by MainConcept AG in its decoder pack.

(I couldn't find these DLLs on a system with Adobe Premiere Elements 10 so that might be an incomplete installation or these files might no longer be used. Web references mention Premiere Elements 2-7.)

One possible issue is that the codec files need to be updated, another is that they are corrupted, and a third is that Firefox simply is not compatible with any version of them.

Because there are many malware-laden codec packages on the web, I would be hesitant to install updates from an unofficial source if neither Adobe nor MainConcept can help. Instead, I would research a way to bypass these files by having Windows use its own built-in media features instead. (Time doesn't permit me to search for how to do that this morning.)

The crash report refers to two components -- ad2mpegin.dll and ad2mpgdmux.dll -- as the last bits of software Firefox (or the active plugin) was running. Based on some web searching, these are codec files installed by Adobe Premiere (or Premiere Elements) supplied by MainConcept AG in its decoder pack. (I couldn't find these DLLs on a system with Adobe Premiere Elements 10 so that might be an incomplete installation or these files might no longer be used. Web references mention Premiere Elements 2-7.) One possible issue is that the codec files need to be updated, another is that they are corrupted, and a third is that Firefox simply is not compatible with any version of them. Because there are many malware-laden codec packages on the web, I would be hesitant to install updates from an unofficial source if neither Adobe nor MainConcept can help. Instead, I would research a way to bypass these files by having Windows use its own built-in media features instead. (Time doesn't permit me to search for how to do that this morning.)

Question owner

Ooh, so that's Adobe Premiere's fault. I think I got a demo cd from someone at some point but I'm no longer using this stuff, so I won't be reluctant to get rid of it.

I also did try to track down the .dll files separately, I hope it will resolve the problem. I'll keep testing.

Ooh, so that's Adobe Premiere's fault. I think I got a demo cd from someone at some point but I'm no longer using this stuff, so I won't be reluctant to get rid of it. I also did try to track down the .dll files separately, I hope it will resolve the problem. I'll keep testing.

Question owner

Yeah, it seems the .dll files were causing the problem! No crash happened since I've cleared all Adobe Premiere stuff. Which is kind of weird, because the .dlls were not the cause of crash in the previous crash reports...? But still, the browser is working just fine. Thank you very much for the help!!!

Yeah, it seems the .dll files were causing the problem! No crash happened since I've cleared all Adobe Premiere stuff. Which is kind of weird, because the .dlls were not the cause of crash in the previous crash reports...? But still, the browser is working just fine. Thank you very much for the help!!!