Closed
Bug 803796
Opened 12 years ago
Closed 4 years ago
Implement non-fatal assertion and error message instead of crashing for unsupported devices
Categories
(Firefox for Android Graveyard :: General, defect, P5)
Tracking
(firefox17-, fennec+)
RESOLVED
INCOMPLETE
People
(Reporter: scoobidiver, Unassigned)
References
Details
Attachments
(1 file)
13.21 KB,
application/vnd.oasis.opendocument.spreadsheet
|
Details |
ARMv7 devices with an unsupported GPU make Firefox crash on startup for various reasons:
* OpenGL ES 2.0 not supported: bug 778175
* OpenGL ES 2.0 supported but Vivante GPU driver bug: bug 771774
* OpenGL ES 2.0 supported but unknown graphic driver bug: bug 783196
We should blocklist them like in bug 775237 for ARMv6 devices.
Reporter | ||
Updated•12 years ago
|
Comment 1•12 years ago
|
||
I believe we blocked all devices we could find in the play store that were crashing. There are a non-zero number of devices that do not have a play store entry thus cannot be blocked. There was a suggestion of having the assertion be non-fatal and providing some error message.
Reporter | ||
Comment 2•12 years ago
|
||
Based on https://crash-analysis.mozilla.com/rkaiser/2012-10-18/2012-10-18.fennecandroid.beta.17.0.devices.weekly.html#devices, I created an ODS document where I kept devices (ARMv6 & ARMv7) with only crashes on abort (unable to distinguish startup/non-startup crashes and to know the abort message) and filtered those with more than 10 crashes.
Comment 3•12 years ago
|
||
Brad - what do you think of getting someone to follow through with comment 1's suggestion of having a non-fatal assertion and error message? Would this be something that could also be rolled into handling for unsupported ARMv6 devices (thus, something probably desirable for 17)?
Assignee: nobody → blassey.bugs
Reporter | ||
Updated•12 years ago
|
Summary: sync device exclusions for unsupported ARMv7 devices → Implement non-fatal assertion and error message instead of crashing for unsupported devices
Comment 4•12 years ago
|
||
Not tracking 17, we block list these things in the market for release, not in the product.
Updated•12 years ago
|
tracking-fennec: ? → +
Comment 6•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 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
•