EMET causes DEP failure on shutdown of plugin-container.exe




6 years ago
4 months ago


(Reporter: Ben Turner (not reading bugmail, use the needinfo flag!), Unassigned)


Firefox Tracking Flags

(Not tracked)



I use EMET (http://support.microsoft.com/kb/2458544) to enforce DEP on all apps. Every time I shut firefox down I see this in my logs:

  EMET_DLL module logged the following event:
    EMET detected DEP mitigation and will close the application:
    C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe

That's unfortunately it, I don't see anything else that can help pinpoint the problem.

Filing this mostly to get some windows experts and s-g eyes on the problem to see how much we care.
Summary: EMET causes DEP failure on shutdown → EMET causes DEP failure on shutdown of plugin-container.exe
What plugin is running inside the container?
Always flash. I have 11.3.300.257 now but it happened on the previous version too.

Comment 3

6 years ago
What does that "DEP mitigation" message mean?
I think it means that some data section was being executed.

Comment 5

6 years ago
Was this with the new version of Flash and before bug 747683 landed?
I didn't install the new EMET and enable it for plugin-container until pretty recently so I don't know how long ago this started happening. I do, however, have an entry in my log from 6/9 fingering plugin-container, which was before both the new version of flash and the landing of bug 747683.
This is being discussed in a public forum so we can probably unhide the bug

Some of the later comments say Firefox 13.0.1 resolved the problem, does Ben's build have https://hg.mozilla.org/mozilla-central/rev/8cf5423b0213 (patch from bug 747683)?


6 years ago
Group: core-security

Comment 8

5 years ago
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:26.0) Gecko/20100101 Firefox/26.0

guessing that the commit should been in the build i'm having, however, "crashes" (e. g. the DEP mitigation messages) have started happening with the branch change; pre-26, i never got hit by it.

at this time, it *seems* to be related to bug 901963


4 months ago
Last Resolved: 4 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.