Closed Bug 1262678 Opened 8 years ago Closed 5 years ago

crash in mozilla::image::FrameAnimator::DrawFrameTo

Categories

(Core :: Graphics: ImageLib, defect, P3)

44 Branch
x86
Windows 7
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox45 --- affected
firefox46 --- affected
firefox47 --- affected
firefox48 --- affected
firefox-esr45 --- affected

People

(Reporter: alex_mayorga, Unassigned)

Details

(Keywords: crash, Whiteboard: [gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-13048b67-33df-482d-a48a-747c32160407.
=============================================================

¡Hola!

21 crashes (6 startup) in the past month at https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=28&signature=mozilla%3A%3Aimage%3A%3AFrameAnimator%3A%3ADrawFrameTo

Filing per https://bugzilla.mozilla.org/show_bug.cgi?id=1219672#c19
:seth, can you look into a bug since FrameAnimator::DrawFrameTo() is implemented by you?
Flags: needinfo?(seth)
Component: Graphics → ImageLib
Whiteboard: [gfx-noted]
Updating crash signature to reflect changes to signature generation made in bug 1269817 (although reports older than a week will not be reprocessed), and adding dependency to ShutDownKill metabug.

(These probably shouldn't all be separate bugs, but I'm not going to fix that up in a mass-change.)
Blocks: shutdownkill
Crash Signature: [@ mozilla::image::FrameAnimator::DrawFrameTo] → [@ IPCError-browser | ShutDownKill ]
In this case I should probably undo that, since there are non-ShutDownKill crashes mixed in here.

However, the crash in comment 0 is *not* representative of this bug since it is a ShutDownKill crash and would now have an entirely different signature.
No longer blocks: shutdownkill
Crash Signature: [@ IPCError-browser | ShutDownKill ] → [@ mozilla::image::FrameAnimator::DrawFrameTo]
Flags: needinfo?(seth.bugzilla)

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.