This bug was filed from the Socorro interface and is report bp-493f3053-24ff-4c07-918e-5bd3f2131128. ============================================================= Go to http://acko.net/blog/on-asmjs/ using Firefox 26 beta (the latest one as of today/yesterday), and you'll get an instant crash. I'm using a Galaxy Nexus.
Another report: bp-d9b508af-c5f7-4ecc-a79c-071052131127
I'm on Galaxy Nexus 4.3, kernel version 3.0.72-gfb3c9ac, build number JWR66Y.
I updated Firefox Nightly and it crashed too: bp-03a51241-1f23-41ab-b8f0-dd6052131128
Does this reproduce on other devices as well? Are there any URLs in the crash reports that are from more widely used sites?
This is a graphics driver crash and will affect any device that contains a PowerVR chip. It seems to be rather low volume 17 crashes over the last seven days. This particular signature is Galaxy Nexus only. However each OEM can make minor changes to the driver or Android which can cause the offset to be different. The other common PowerVR devices are the Samsung Tab 2.0 seven and ten inch models.
> This is a graphics driver crash Jeff mentioned to me in-person that even if the graphics driver is bad, we shouldn't propagate the crashiness out to Firefox (or something like that), so we can still probably fix this somehow.
In that case we don't need to track this low volume crash for release blocking but can look at an uplift nomination to branches when a fix is verified.
Yep, we should try to figure out what we're tickling in the driver to cause this crash, then work around it for this driver.
Oops, we don't actually know if this is a WebGL or layers issue yet.
I looked at this briefly. It appears to be crashing in WebGL during TexSubImage2D(). I don't know if it's a bounds issue or what.
filter on [mass-p5]
Closing this bug as there have been zero reports in over a year. Please reopen if this still reproduces for you in the latest Fennec.