Firefox 28 crashing on close
Win 8.1 Enterprise Update1 x64. is there a known issue and/or fix?
from windows event viewer:
Log Name: Application Source: Application Error Date: 4/17/2014 7:56:46 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: mycomp.fqdn Description: Faulting application name: firefox.exe, version: 28.0.0.5186, time stamp: 0x53240e37 Faulting module name: xul.dll, version: 28.0.0.5186, time stamp: 0x53240e04 Exception code: 0xc0000005 Fault offset: 0x00184729 Faulting process id: 0x5c0 Faulting application start time: 0x01cf5ab1af72b5a2 Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe Faulting module path: C:\Program Files (x86)\Mozilla Firefox\xul.dll Report Id: 138ca4ff-c6a5-11e3-8265-0022153bd1de Faulting package full name: Faulting package-relative application ID:
Win 8.1 Enterprise Update1 x64. is there a known issue and/or fix?
from windows event viewer:
<pre><nowiki>Log Name: Application
Source: Application Error
Date: 4/17/2014 7:56:46 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: mycomp.fqdn
Description:
Faulting application name: firefox.exe, version: 28.0.0.5186, time stamp: 0x53240e37
Faulting module name: xul.dll, version: 28.0.0.5186, time stamp: 0x53240e04
Exception code: 0xc0000005
Fault offset: 0x00184729
Faulting process id: 0x5c0
Faulting application start time: 0x01cf5ab1af72b5a2
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files (x86)\Mozilla Firefox\xul.dll
Report Id: 138ca4ff-c6a5-11e3-8265-0022153bd1de
Faulting package full name:
Faulting package-relative application ID:</nowiki></pre>
cor-el moo ko soppali ci
All Replies (1)
If you have submitted crash reports then please post the IDs of one or more recent crash reports that have a "bp-" prefix:
- bp-xxxxxxxx-xxxx-xxxx-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, like you open a website, or open the crash reports page via "Help > Troubleshooting Information".
See: