Closed
Bug 705874
Opened 13 years ago
Closed 12 years ago
Binary XML file line #6: Error inflating class org.mozilla.gecko.BrowserToolbar (Startup crash on Android 2.1)
Categories
(Firefox for Android Graveyard :: General, defect, P5)
Tracking
(firefox11 verified, firefox12 verified, firefox13 verified, fennec11+)
VERIFIED
FIXED
Firefox 13
People
(Reporter: nbp, Assigned: sriram)
References
()
Details
(Keywords: crash, relnote, Whiteboard: [native-crash][eclair] [blacklist], startupcrash[inbound])
Attachments
(2 files)
8.99 KB,
text/plain
|
Details | |
12.83 KB,
patch
|
mfinkle
:
review+
akeybl
:
approval-mozilla-aurora+
akeybl
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
version: Nightly -- fennec-11.0a1.en-US.android-arm-1.apk (13.70 M) downloaded the 11-28 13:10 The logcat is available at http://pastebin.mozilla.org/1388756 About the phone: Type: Samsung Galaxy S 1 Model: GT-I9000 Firmware: 2.1-update1 Baseband: I9000XXJF3 Kernel: 2.6.29 umts_scm@S1-BUILD05 #2 Build: ECLAIR
Comment 1•13 years ago
|
||
The logcat is not available anymore. Can you upload it again and change the "How long should your post be retained?" setting to forever?
Updated•13 years ago
|
Severity: normal → critical
Comment 2•13 years ago
|
||
sounds like a 2.1 crasher. will start adding [eclair] to the whiteboard to track these bugs
Whiteboard: [native-crash] → [native-crash][eclair]
Comment 3•13 years ago
|
||
ram - can you list the devices that have this problem - we probably want to just mark these devices as unsupported.
Assignee: nobody → sriram
Assignee | ||
Comment 4•13 years ago
|
||
This is usually caused in 2.1 devices. I'm not sure if it's a problem with AT&T locked phones though. http://stackoverflow.com/questions/7619945/android-resources-not-found-on-some-devices -- this specifies the exact problem observed. Also, most of the APIs we use are targeted for level 8 and not 5. This could cause even more crashes. (The best way to see if we are API level 5 complaint is by using Romaxa's scripts and loading our project in eclipse. Eclipse will check every line against the specified SDK and will show as where we are not using API level 5 methods).
Updated•13 years ago
|
Keywords: relnote
Priority: -- → P2
Whiteboard: [native-crash][eclair] → [native-crash][eclair] [blacklist]
Comment 5•13 years ago
|
||
We should blocklist the bad phones or just drop eclair support
Updated•13 years ago
|
tracking-fennec: --- → 11+
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Sriram Ramasubramanian [:sriram] from comment #4) > This is usually caused in 2.1 devices. I'm not sure if it's a problem with > AT&T locked phones though. My phone was unlocked when I bought it in France. (mid September 2010) About the logcat, I can ask someone to dump one again because I no longer have it.
Comment 8•12 years ago
|
||
dropping priority. we could be dropping 2.1 support too.
Severity: critical → normal
Priority: P2 → P5
Updated•12 years ago
|
Severity: normal → critical
Comment 9•12 years ago
|
||
Logcat attached.
Assignee | ||
Comment 10•12 years ago
|
||
We are using both "match_parent" and "fill_parent" on XML layout files (and some parts of code). http://developer.android.com/reference/android/view/ViewGroup.LayoutParams.html#MATCH_PARENT -- is introduced only in API Level 8. This could be a reason for the crash.
Updated•12 years ago
|
Whiteboard: [native-crash][eclair] [blacklist] → [native-crash][eclair] [blacklist], startupcrash
Updated•12 years ago
|
Summary: Binary XML file line #6: Error inflating class org.mozilla.gecko.BrowserToolbar (Startup crash) → Binary XML file line #6: Error inflating class org.mozilla.gecko.BrowserToolbar (Startup crash on Android 2.1)
Comment 11•12 years ago
|
||
Attachment #592997 -
Flags: review?(mark.finkle)
Comment 12•12 years ago
|
||
Comment on attachment 592997 [details] [diff] [review] patch to use fill_parent instead of match_parent Brad mentioned that only the XML is a problem. The Java constants are the same value. Let's see if this works.
Attachment #592997 -
Flags: review?(mark.finkle) → review+
Updated•12 years ago
|
Target Milestone: --- → Firefox 13
Comment 13•12 years ago
|
||
This issue occurs on the latest Nightly build for Samsung Galaxy S (2.1). Log: http://pastebin.mozilla.org/1471130 -- Mozilla/5.0 (Android;Linux armv7l;rv:13.0a1)Gecko/20120201 Firefox/13.0a1 Fennec/13.0a1 Device: Samsung Galaxy S OS: Android 2.1-update1
Comment 14•12 years ago
|
||
From the log: E/AndroidRuntime( 3862): Caused by: android.content.res.Resources$NotFoundException: File ... E/AndroidRuntime( 3862): Caused by: org.xmlpull.v1.XmlPullParserException: Binary XML file line #5: <bitmap> requires a valid src attribute Which is: http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/resources/drawable/address_bar_bg.xml#6 Is something about that "src" value not legal?
Comment 15•12 years ago
|
||
(In reply to Cristian Nicolae (:xti) from comment #13) > This issue occurs on the latest Nightly build for Samsung Galaxy S (2.1). > > Log: http://pastebin.mozilla.org/1471130 What's in that log is a different bug. Can you file a new bug to track it separately? (In reply to Mark Finkle (:mfinkle) from comment #14) > From the log: > > E/AndroidRuntime( 3862): Caused by: > android.content.res.Resources$NotFoundException: File > ... > E/AndroidRuntime( 3862): Caused by: org.xmlpull.v1.XmlPullParserException: > Binary XML file line #5: <bitmap> requires a valid src attribute > > Which is: > http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/resources/ > drawable/address_bar_bg.xml#6 > > Is something about that "src" value not legal? Yea, it doesn't exist on eclair. In fact, none of our drawables do.
Comment 16•12 years ago
|
||
btw... landed this on inbound, changeset ab671e01a7da
Whiteboard: [native-crash][eclair] [blacklist], startupcrash → [native-crash][eclair] [blacklist], startupcrash[inbound]
Comment 17•12 years ago
|
||
(In reply to Brad Lassey [:blassey] from comment #15) > (In reply to Cristian Nicolae (:xti) from comment #13) > > This issue occurs on the latest Nightly build for Samsung Galaxy S (2.1). > > > > Log: http://pastebin.mozilla.org/1471130 > What's in that log is a different bug. Can you file a new bug to track it > separately? I file bug 723151 for it
Comment 18•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/ab671e01a7da
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 19•12 years ago
|
||
Comment on attachment 592997 [details] [diff] [review] patch to use fill_parent instead of match_parent [Approval Request Comment] Regression caused by (bug #): User impact if declined: crash on startup on eclair Testing completed (on m-c, etc.): Risk to taking this patch (and alternatives if risky): String changes made by this patch:
Attachment #592997 -
Flags: approval-mozilla-beta?
Attachment #592997 -
Flags: approval-mozilla-aurora?
Comment 20•12 years ago
|
||
Verified fixed on: Mozilla/5.0 (Android;Linux armv7l;rv:13.0a1)Gecko/20120203 Firefox/13.0a1 Fennec/13.0a1 Device: Samsung Galaxy S OS: Android 2.1-update1
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
status-firefox12:
--- → affected
status-firefox13:
--- → fixed
Comment 21•12 years ago
|
||
Reopening bug for aurora nom
Status: VERIFIED → RESOLVED
Closed: 12 years ago → 12 years ago
Updated•12 years ago
|
status-firefox11:
--- → affected
Comment 22•12 years ago
|
||
Comment on attachment 592997 [details] [diff] [review] patch to use fill_parent instead of match_parent [Triage Comment] Mobile only - approved for Aurora 12 and Beta 11.
Attachment #592997 -
Flags: approval-mozilla-beta?
Attachment #592997 -
Flags: approval-mozilla-beta+
Attachment #592997 -
Flags: approval-mozilla-aurora?
Attachment #592997 -
Flags: approval-mozilla-aurora+
Comment 25•12 years ago
|
||
Crash no longer reproducible. Verified fixed on: Firefox 11 (tinderbox build): 1328844077/09-Feb-2012 20:42 20120209192117 Firefox 12: Firefox 12.0a2 (2012-02-09) Firefox 13: Firefox 13.0a1 (2012-02-09) Device: Samsung Galaxy S Captivate OS: Android 2.1-update1
Status: RESOLVED → VERIFIED
Updated•3 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
•