Closed
Bug 739445
Opened 14 years ago
Closed 10 years ago
Firefox hang | F374527877_____________________________________________
Categories
(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)
External Software Affecting Firefox Graveyard
Flash (Adobe)
x86
Windows NT
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: marcia, Unassigned)
Details
(Keywords: hang)
Crash Data
This bug was filed from the Socorro interface and is
report bp-ee5137cb-d577-4b8b-be69-851812120326 .
=============================================================
Seen while looking at the explosive report: https://crash-stats.mozilla.com/report/list?signature=hang%20|%20F374527877_____________________________________________
The signature summary shows a spike in number of crashes in 11.0 compared to other releases. The largest number of crashes happen with 11.1.x versions of Flash.
There were also some other plugin spikes noted in the latest explosive report: https://crash-analysis.mozilla.com/rkaiser/2012-03-25/2012-03-25.firefox.11.explosiveness.html that show similar spikes in 11.1.x flash versions.
Updated•14 years ago
|
Component: Plug-ins → Flash (Adobe)
Product: Core → Plugins
QA Contact: plugins → adobe-flash
Version: 11 Branch → 11.x
Comment 1•14 years ago
|
||
These numbers may change now that version 11.2.202.228 has been released (3/27/2012).
Comment 2•10 years ago
|
||
I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Comment 3•10 years ago
|
||
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 11.x → unspecified
Updated•4 years ago
|
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•