crash in libskia.so@0x104ffe

NEW
Unassigned

Status

()

Firefox for Android
General
--
critical
3 years ago
3 years ago

People

(Reporter: snorp, Unassigned)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

This bug was filed from the Socorro interface and is 
report bp-fd234197-6c3a-4eb9-9710-e80532140921.
=============================================================
Seeing this a lot on Nightly. Did we turn on Skis content?
Flags: needinfo?(milan)
Skia content, that is. Stupid phone.
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)
(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).
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...
(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.
This is system skia, not skia in our tree.
You need to log in before you can comment on or make changes to this bug.