Closed
Bug 1070741
Opened 11 years ago
Closed 7 years ago
crash in libskia.so@0x104ffe
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: snorp, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-fd234197-6c3a-4eb9-9710-e80532140921.
=============================================================
| Reporter | ||
Comment 1•11 years ago
|
||
Seeing this a lot on Nightly. Did we turn on Skis content?
Flags: needinfo?(milan)
| Reporter | ||
Comment 2•11 years ago
|
||
Skia content, that is. Stupid phone.
Comment 3•11 years ago
|
||
Didn't turn on Skia content (at least on purpose.) This isn't somebody just playing with the non-default to see how it works?
Flags: needinfo?(milan)
| Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #3)
> Didn't turn on Skia content (at least on purpose.) This isn't somebody just
> playing with the non-default to see how it works?
This is from my own device, and I haven't done anything special. Checked just now and I have gfx.content.azure.backends = cairo (the default).
Comment 5•11 years ago
|
||
Do the red lines in the crash report mean we don't have a good confidence the stack is correct? 'Cause that would explain it...
| Reporter | ||
Comment 6•11 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #5)
> Do the red lines in the crash report mean we don't have a good confidence
> the stack is correct? 'Cause that would explain it...
It means we don't have a symbol for that address, which does basically mean we don't know if that's valid or not. Might not be skia related.
Comment 7•11 years ago
|
||
This is system skia, not skia in our tree.
Comment 8•7 years ago
|
||
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•