Closed
Bug 665067
Opened 13 years ago
Closed 7 years ago
Firefox crash @0x1a2710 or @0x1b2710 (malware-related?)
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: marcia, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-5d4fbdf9-c845-4162-ad54-898f32110617 . ============================================================= Seen while reviewing crash stats. Seen across all versions. #2 crash in https://crash-analysis.mozilla.com/chofmann/20110616/top-50-after-20110608000000.html. https://crash-stats.mozilla.com/report/index/5d4fbdf9-c845-4162-ad54-898f32110617 Frame Module Signature [Expand] Source 0 @0x1a2710 1 @0x1a2869 2 @0x1a5a7a 3 @0x937297
Reporter | ||
Comment 1•13 years ago
|
||
This showed up on the explosive report today: http://test.kairo.at/socorro/2011-06-16.firefox.4.0.explosiveness.html
Comment 2•13 years ago
|
||
It is now #3 top browser crasher in 5.0 over the last 3 days. It started on June 11 and was high on June 13. It happens only on Windows XP. One comment says: "I have this problem ever since i had a virus with iexplore.exe" So I think it is malware-related.
OS: Windows NT → Windows XP
Summary: Firefox crash @0x1a2710 → Firefox crash @0x1a2710 (malware-related?)
Comment 3•13 years ago
|
||
I added another similar crash signature which is currently #46 top browser crasher in 5.0: Frame Module Signature [Expand] Source 0 @0x1b2710 1 @0x1b2869 2 @0x1b5a7a 3 @0x1ce
Crash Signature: [@ @0x1a2710] → [@ @0x1a2710][@ @0x1b2710 ]
Summary: Firefox crash @0x1a2710 (malware-related?) → Firefox crash @0x1a2710 or @0x1b2710 (malware-related?)
Updated•13 years ago
|
Blocks: malware-attacks
Updated•9 years ago
|
Crash Signature: [@ @0x1a2710][@ @0x1b2710 ] → [@ @0x1a2710]
[@ @0x1b2710 ]
Comment 4•7 years ago
|
||
I'm marking this bug as WORKSFORME as bug crashlog signature didn't appear from a long time (over half year) in Firefox.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•