Closed Bug 985121 Opened 10 years ago Closed 9 years ago

Crash in[@ PathFromRegionInternal ]

Categories

(Core :: Graphics, defect)

28 Branch
x86_64
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: tdowner, Unassigned)

References

Details

(Keywords: crash)

Crash Data

+++ This bug was initially created as a clone of Bug #956967 +++
We are seeing this crash (Supposedly fixed in 28) on SUMO at https://support.mozilla.org/en-US/questions/990511

https://crash-stats.mozilla.com/report/index/574bbe74-3d41-4f94-b557-37f822140318
There might be some edge case that wasn't addressed by bug 956967 as QA tested and verified the bug was fixed. Based on the reports so far there are 25 reports with 8 dupes using Firefox 28.0 20140314220517 (the build we just released).

More Reports:
https://crash-stats.mozilla.com/report/list?product=Firefox&signature=PathFromRegionInternal
There's another user on SUMO @ https://support.mozilla.org/en-US/questions/991667 experiencing the same issue. Quite a long list of crash reports all yielding the @ PathFromRegionInternal signature.
This user (fx29 on windows 8.1) reports that turning hardware acceleration off is a workaround (though not pleasant). https://support.mozilla.org/en-US/questions/997555
Looks like it's still an extremely low-volume crash, but very unlikely we're going to find a useful regression range for it at this point.
https://crash-stats.mozilla.com/report/index/6c64d086-6314-4013-858b-c23132151006
I actually only see three reports of this crash over the last month. Two of the crashes are with 41.0b99 from the same user and one is with Firefox 41.0.1. I don't believe this meets the threshold of something we should investigate. Closing as incomplete.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.