Crash in [@ org.xmlpull.v1.XmlPullParserException: at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java)]

RESOLVED FIXED in Firefox 70

Status

()

defect
P2
critical
RESOLVED FIXED
Last month
2 hours ago

People

(Reporter: marcia, Assigned: petru)

Tracking

({crash, regression})

Firefox 68
Firefox 70
ARM
Android
Points:
---
Bug Flags:
qe-verify +

Firefox Tracking Flags

(firefox-esr68 affected, firefox68 wontfix, firefox69 affected, firefox70 fixed)

Details

(crash signature)

Attachments

(1 attachment)

This bug is for crash report bp-0f9b8484-cb16-4f6e-aa3d-e746e0190515.

Crash seen while reviewing 68.0b5 crashes. Crashes go back to at least 20190510095015 when Fennec was in nightly: https://bit.ly/2IdLX5Z. Currently in beta 5 this is in the top 20 list of crashes.

Comments and correlations don't look particularly useful. No real pattern in the few URLs. APIs range from 16-19.

Java stack trace:

org.xmlpull.v1.XmlPullParserException: Binary XML file line #1: invalid drawable tag vector
	at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:986)
	at android.graphics.drawable.Drawable.createFromXml(Drawable.java:930)
	at android.content.res.Resources.loadDrawable(Resources.java:3436)
	at android.content.res.Resources.getDrawable(Resources.java:1917)
	at org.mozilla.gecko.FindInPageBar.updateFindTextError(FindInPageBar.java:166)
	at org.mozilla.gecko.FindInPageBar.onMatchesCountResult(FindInPageBar.java:150)
	at org.mozilla.gecko.FindInPageBar.handleMessage(FindInPageBar.java:237)
	at org.mozilla.gecko.EventDispatcher$3.run(EventDispatcher.java:368)
	at android.os.Handler.handleCallback(Handler.java:733)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:146)
	at android.app.ActivityThread.main(ActivityThread.java:5602)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:515)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1283)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
	at dalvik.system.NativeStart.main(Native Method)

Some of the crash comments mention crashing when searching, specifically on wikipedia.

I tried to reproduce this issue following some scenarios on Wikipedia but I wasn't able to find the crash.

  • searching from the page search bar;
  • searching on Wikipedia the copied text;
  • making Wikipedia the search engine;
  • using the search engine icon;
  • Selecting an option from the search bar of Wikipedia;

Devices:

  • Samsung Galaxy S8 (Android 9);
  • Motorola Moto G6 (Android 8);
  • Nokia 6 (Android 7.1.1).

Builds:

  • Nightly 68.0a1 (2019-06-05);
  • Beta 68.0b5;
  • Beta 68.0b7.

I'll keep an eye on my daily work to see if I can track the problem.

Triaging as P2 for now. Will keep an eye on this as we continue through the 68 cycle.

Priority: -- → P2

This crash is continuing to be visible on 68 release. No useful comments. Samsung and asus devices are the top crashing devices, running older APIs 17-19.

I hit this crash too on a Samsung Tab running Android 4.2.2.
I was browsing likes on a Facebook profile when it happened.
bp-ba5dc5a9-a65c-4e3a-acae-acccb0190712
bp-60ae357d-f421-40bf-be4b-aabe60190712

Hi,

I also get this crash ( https://crash-stats.mozilla.org/report/index/38596be2-2f33-41d9-8989-a3f660190712 and others) on asus memopad hd7 ME173X, android 4.2.2

If it help, I can reliably trigger the crash if I search inside the page (for any page, including about:crashes or others) for a sequence of character not present (such as 'iii' ) , it crashes at the third character.

Actually, I must amend my previous statement, it crashes at the first character not found when I search inside a page.

I can also trigger a freeze with the same steps on ff 68 on android 4.4 (lg G tab 8.3) but I didn't manage to get a crash log.

No issue on android 7.0 (motoG 3) and 9.0 (oneplus 3t).

let me know which information/test can help you.

regards

Hardware: Unspecified → ARM

Hi,

I managed to narrow the crash between nighty 2019-04-24-09-53-59-mozilla-central-android-api-16 (last good) and nighly 2019-04-25-09-46-25-mozilla-central-android-api-16 (first bad)

For an unkwown reason, I don't get the crash reporter before a nightly in may, it just crash.

Asus memopad hd7 me173x , android 4.2

Bug 1345104 is in that range and looks like a good candidate given the STR from comment 6.

Flags: needinfo?(petru.lingurar)
Regressions: 1345104
Flags: needinfo?(andrei.teslovan)
Assignee: nobody → petru.lingurar
Status: NEW → ASSIGNED
Flags: needinfo?(petru.lingurar)

Thanks Mjules, indeed, this is trivial to reproduce with your STRs.

Flags: needinfo?(andrei.teslovan)

VectorDrawableCompat allows backwards compatibility up to API 14.

Keywords: checkin-needed

Pushed by cbrindusan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dfdb610b82b9
Use VectorDrawableCompat to load the error svg; r=AndreiLazar

Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 7 hours ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70

Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.

Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.