Closed Bug 800569 Opened 12 years ago Closed 6 years ago

Input Indicates that the Droid RAZR is crashing alot with 16 and 17

Categories

(Firefox for Android Graveyard :: General, defect)

16 Branch
ARM
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tdowner, Unassigned)

Details

(Keywords: crash, Whiteboard: [SUMO][native-crash])

This is a significant portion of the crashes on input after 16 was released.
Summary: Input Indicates that the Droid RAZR → Input Indicates that the Droid RAZR is crashing alot with 16
Here are crashes in https://crash-analysis.mozilla.com/rkaiser/2012-10-10/2012-10-10.fennecandroid.release.16.0.devices.html#dev-motorola_droid_razr
It accounts for 0.5% of crashes.

The libutils.so@0x2202e signature looks like bug 749687 but happens only on startup.
Bug 747629 is also hit a lot which is expected.
Keywords: crash
Whiteboard: [SUMO] → [SUMO][native-crash]
Feedback from Beta shows this crash popping up in there as well.
Summary: Input Indicates that the Droid RAZR is crashing alot with 16 → Input Indicates that the Droid RAZR is crashing alot with 16 and 17
Crash stats show nothing worrisome for both so it might be caused by non submitted crash reports.
Could be the XT890 http://pdadb.net/index.php?m=specs&id=3868&c=motorola_razr_i_xt890 as it's an Intel Atom Z2480 chipset attempting to run ARM code, but Google shouldn't be offering the ARM package at all.
This is dying back down on Input, no longer the top crasher. I'll continue to keep an eye on this.
Makes me wonder if these people were running 4.2 pre-release builds or roms that did similar things to what caused issues for us.
No clue if this is still an issue, but I imagine it's not.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.