Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox 30.0b Crashes, EMET 4.1 to blame?

  • 2 replies
  • 21 have this problem
  • 3 views
  • Last reply by GDwarf

GDwarf
GDwarf
more options

Howdy all.

I've relatively recently (past few months) started using Microsoft EMET (https://support.microsoft.com/kb/2458544) to provide extra security for my web browsing. For the most part it works fine with Firefox, but about once or twice a day Firefox will crash, and the errors make it clear that EMET is to blame.

The Windows Event Viewer shows that the plugin container is crashing (see below for a typical entry) on occasion, while my Mozilla crash reports indicate that various parts of FF are crashing after trying to read memory that they shouldn't.

Anecdotally, the crashes seem more common when I load websites that use Flash, though I haven't tested directly to know if this is actually the case or not.

So, my question is if anyone knows what EMET mitigations are known to be FF safe and if there's any hope for having the full suite play nice with the browser.

Typical Windows Event Error:

Faulting application name: plugin-container.exe, version: 30.0.0.5241, time stamp: 0x536c0e03

Faulting module name: mozalloc.dll, version: 30.0.0.5241, time stamp: 0x536bdea6

Exception code: 0x80000003

Fault offset: 0x0000141b

Faulting process id: 0xef4

Faulting application start time: 0x01cf706cd123e963

Faulting application path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe

Faulting module path: C:\Program Files (x86)\Mozilla Firefox\mozalloc.dll

Report Id: ce00c077-dc7d-11e3-8377-f46d0409e237

Faulting package full name:

Faulting package-relative application ID:


The last five crash reports are: bp-6ecba95e-2125-4ead-8aac-297452140515 bp-d48e1d3c-5d1b-47be-92e8-b0e332140515 bp-b9d0c081-2a20-4056-96c9-7763e2140514 bp-5005fda2-cab3-4939-8d8a-993be2140514 bp-b975d529-992d-45f0-823f-ddc182140513

Howdy all. I've relatively recently (past few months) started using Microsoft EMET (https://support.microsoft.com/kb/2458544) to provide extra security for my web browsing. For the most part it works fine with Firefox, but about once or twice a day Firefox will crash, and the errors make it clear that EMET is to blame. The Windows Event Viewer shows that the plugin container is crashing (see below for a typical entry) on occasion, while my Mozilla crash reports indicate that various parts of FF are crashing after trying to read memory that they shouldn't. Anecdotally, the crashes seem more common when I load websites that use Flash, though I haven't tested directly to know if this is actually the case or not. So, my question is if anyone knows what EMET mitigations are known to be FF safe and if there's any hope for having the full suite play nice with the browser. Typical Windows Event Error: Faulting application name: plugin-container.exe, version: 30.0.0.5241, time stamp: 0x536c0e03 Faulting module name: mozalloc.dll, version: 30.0.0.5241, time stamp: 0x536bdea6 Exception code: 0x80000003 Fault offset: 0x0000141b Faulting process id: 0xef4 Faulting application start time: 0x01cf706cd123e963 Faulting application path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe Faulting module path: C:\Program Files (x86)\Mozilla Firefox\mozalloc.dll Report Id: ce00c077-dc7d-11e3-8377-f46d0409e237 Faulting package full name: Faulting package-relative application ID: The last five crash reports are: bp-6ecba95e-2125-4ead-8aac-297452140515 bp-d48e1d3c-5d1b-47be-92e8-b0e332140515 bp-b9d0c081-2a20-4056-96c9-7763e2140514 bp-5005fda2-cab3-4939-8d8a-993be2140514 bp-b975d529-992d-45f0-823f-ddc182140513

Modified by GDwarf

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Try [/questions/993163] Firefox 28 with EMET 4.1

GDwarf
GDwarf Question owner
more options

Thanks for the reply.

However, of the two pieces of advice in that thread one, "Disable EAF mitigation on plugin-container.exe", doesn't work, and the other ("Disable all protection for FF but SEHOP and NUL Page Prealloc") would get rid of most of the security EMET provides.

If, ultimately, it turns out that EMET simply doesn't play nice with FF then alright, but it's just a shame, since it provides a nice extra layer of security against attacks, which seems especially important nowadays.