Closed
Bug 500575
Opened 15 years ago
Closed 13 years ago
top crash [@ ntdll.dll@0x43387][@ imon.dll@0x453d]
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: samuel.sidler+old, Assigned: samuel.sidler+old)
References
()
Details
(Keywords: crash)
Crash Data
Currently, the #7 topcrash in Firefox 3.0.11 happens with a stack signature of ntdll.dll@0x43387. This bug is similar to bug 464213 except that it seems the crash often occurs with the following stack, taken from bp-3d2dd5ec-7a3a-4c1a-bfa4-62be92090625: Frame Module Signature [Expand] Source 0 ntdll.dll ntdll.dll@0x43387 1 ntdll.dll ntdll.dll@0x4323b 2 imon.dll imon.dll@0x453d 3 @0x18eaabc3 This indicates the crash is potentially occurring because of imon.dll, which is associated with ESET's NOD32 antiviral software[1]. I've contacted them to see if we can work to get this issue fixed. Note: This stack signature seems to have three different root causes: Flash, NOD32, and Norton Confidential (coFFPlgn.dll). By far, NOD32 is the most popular in the crashes I sampled, with Norton and Flash as second and third, respectively. [1] http://www.eset.com/products/nod32.php
I made a new bug report with a good reproducible crasher in ntdll.dll. See bug 504416. There is also another recent ntdll.dll bug, bug 503045.
Updated•13 years ago
|
Crash Signature: [@ ntdll.dll@0x43387]
[@ imon.dll@0x453d]
Updated•13 years ago
|
Crash Signature: [@ ntdll.dll@0x43387]
[@ imon.dll@0x453d]
Comment 2•13 years ago
|
||
Not sure what to do with this bug. We no longer have an nt.dll appearing in the top crash list. Since these signatures have changed we can't find this anymore. There is no way we can get from this bug to something actionable. Resolving as works for me since I can't find it. Likely new ntdll issues are logged in new items.
Status: NEW → RESOLVED
Crash Signature: [@ ntdll.dll@0x43387]
[@ imon.dll@0x453d] → [@ ntdll.dll@0x43387]
[@ imon.dll@0x453d]
Closed: 13 years ago
Keywords: topcrash
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•