Closed Bug 1568376 Opened 6 years ago Closed 3 years ago

Crash in [@ DWriteGlyphLookupCache::FillGlyphBitmap]

Categories

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

Unspecified
Windows 8
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox70 --- affected

People

(Reporter: lizzard, Unassigned)

Details

(Keywords: crash, Whiteboard: qa-not-actionable)

Crash Data

A few crashes from the 20190721094948 build.

Very low volume, the four recent crashes in nightly 70 are all in the same build on an AMD CPU with the same crash address 0x7ffed9d1f0a1 and EXCEPTION_PRIV_INSTRUCTION. I'm unfamiliar with this error, I wonder if it is an alignment issue (considering the crash address).

Some of the older ones (when aggregating all crashes in DWriteGlyphLookupCache::FillGlyphBitmap) have different crash addresses like 0x0 and also different exceptions.

At least for the recent ones it could be a bug in DWrite but the volume at this point is too low to blocklist. I don't want to be too quick to invoke The AMD Bug but at a superficial level there are intriguing similarities. I'll try to dig into a minidump if I find the time.

Priority: -- → P3
Whiteboard: qa-not-actionable

Closing because no crashes reported for 12 weeks.

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