Crash in F_1371125________________________________________________

NEW
Unassigned

Status

defect
--
critical
Last year
13 days ago

People

(Reporter: marcia, Unassigned)

Tracking

({crash})

unspecified
x86
Windows 7

Firefox Tracking Flags

(firefox-esr60 affected, firefox61 wontfix, firefox62 wontfix, firefox63 wontfix, firefox65 affected, firefox66 affected, firefox67 affected, firefox68 affected, firefox69 affected, firefox70 affected)

Details

(crash signature)

This bug was filed from the Socorro interface and is
report bp-57a9de56-29c1-4351-9d7d-9afa50180710.
=============================================================

Current the #13 top crash in 61.0.1. Filing since there is no bug associated with it: https://bit.ly/2L6As0z. Windows 7 has the highest number of crashes.

Top 10 frames of crashing thread:

0 npswf32_30_0_0_113.dll F_1371125________________________________________________ F_766591945____________________________________________________________________:234
1 npswf32_30_0_0_113.dll F_652032984_____________________________________________________ F_1951567228__________________________________________________________:261
2 npswf32_30_0_0_113.dll F1607135317_____________________________________________________________________ F_851861807__________________________________________________________:139
3 npswf32_30_0_0_113.dll F2166389_____________________________________________________________________ F_851861807__________________________________________________________:576
4 npswf32_30_0_0_113.dll F_917831355____________________________________________ F_851861807__________________________________________________________:493
5 npswf32_30_0_0_113.dll F1315696776________________________________ F_851861807__________________________________________________________:444
6 npswf32_30_0_0_113.dll F_1428703866________________________________ F_766591945____________________________________________________________________:203
7 npswf32_30_0_0_113.dll F845925699_____________________________________ F1677514683__________________________________________________________________________________:104
8 npswf32_30_0_0_113.dll F_274593382________________________________ F209679109___________________________________________________________________________________:1803
9 npswf32_30_0_0_113.dll F_305312235__________________________________________ F209679109___________________________________________________________________________________:1051

=============================================================
Hi Jeromie, we're seeing this signature spike pretty heavily recently. Is this something you'd be able to look into?
Flags: needinfo?(jeclark)
Absolutely, thanks for the report.  I've opened FLASH-4190453 for this.
Flags: needinfo?(jeclark)

Marcia, we see a precipitous drop in reports after October, but I can't tie this to a specific changelist. It appears to be fixed (or at least back to baseline). There's no obvious smoking gun in the stack to drive useful further investigation.

Flags: needinfo?(mozillamarcia.knous)

(In reply to Jeromie Clark from comment #3)

Marcia, we see a precipitous drop in reports after October, but I can't tie this to a specific changelist. It appears to be fixed (or at least back to baseline). There's no obvious smoking gun in the stack to drive useful further investigation.

Yes, I can definitely see the dropoff in the graph. For 63 and 64 it looks like we were under 200 crashes. We can see if that stays the course on 65.

Flags: needinfo?(mozillamarcia.knous)
Crash Signature: [@ F_1371125________________________________________________] → [@ F_1371125________________________________________________] [@ F_67009659______________________ ]

I don't know why I updated the status flags, but I guess the update is correct so I'm not going to undo it.

68/69/70 are affected. Current correlations: (95.32% in signature vs 00.43% overall) Module "NPSWF32_32_0_0_223.dll" = true
(95.32% in signature vs 00.43% overall) flash_version = 32.0.0.223

2142 current crashes during the 68 release cycle.

You need to log in before you can comment on or make changes to this bug.