1006631 - crash in android.content.res.Resources$NotFoundException: Resource is not a ColorStateList (color or path): TypedValue{t=0x1/d=0x7f0d0076 a=3 r=0x7f0d0076} at android.content.res.Resources.loadColorStateList(Resources.java)

Status: RESOLVED DUPLICATE of bug 1067429

(Firefox for Android Graveyard :: General, defect)

Description

[Aaron Train [:aaronmt]]

This bug was filed from the Socorro interface and is 
report bp-85f9cf76-1af1-4e36-8db2-024172140501.
=============================================================

android.content.res.Resources$NotFoundException: Resource is not a ColorStateList (color or path): TypedValue{t=0x1/d=0x7f0d0076 a=3 r=0x7f0d0076}
	at android.content.res.Resources.loadColorStateList(Resources.java:2023)
	at android.content.res.TypedArray.getColorStateList(TypedArray.java:342)
	at android.widget.TextView.<init>(TextView.java:788)
	at android.widget.TextView.<init>(TextView.java:480)
	at java.lang.reflect.Constructor.constructNative(Native Method)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:416)
	at android.view.LayoutInflater.createView(LayoutInflater.java:576)
	at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
	at android.view.LayoutInflater.onCreateView(LayoutInflater.java:644)
	at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:669)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:724)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:479)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:391)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:347)
	at android.widget.Toast.makeText(Toast.java:247)
	at android.widget.Toast.makeText(Toast.java:270)
	at org.mozilla.gecko.home.HomeFragment$RemoveHistoryTask.onPostExecute(HomeFragment.java:277)
	at org.mozilla.gecko.util.UiAsyncTask$BackgroundTaskRunnable$1.run(UiAsyncTask.java:56)
	at android.os.Handler.handleCallback(Handler.java:587)
	at android.os.Handler.dispatchMessage(Handler.java:92)
	at android.os.Looper.loop(Looper.java:132)
	at android.app.ActivityThread.main(ActivityThread.java:4123)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:491)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
	at dalvik.system.NativeStart.main(Native Method)

This is a crash solely thus far on the GT-P6210	(Galaxy Tab Plus 7")

Comment 1

[Richard Newman [:rnewman]]

This implies a build with corrupt resources.

Comment 2

[Nick Alexander :nalexander [he/him]]

I'm not so sure this is a build issue.  Looks a great deal like https://bugzilla.mozilla.org/show_bug.cgi?id=866501, which is actually a coding error.  I'll try to look into this.

Comment 3

[Aaron Train [:aaronmt]]

Number of crashes on 33 with the same device/API 13 (3.2)

Comment 4

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Just to get more visibility: Nick, have you had a chance to look into this?

Comment 5

[Nick Alexander :nalexander [he/him]]

(In reply to Michael Comella (:mcomella) from comment #4)
> Just to get more visibility: Nick, have you had a chance to look into this?

Yeah.  It's fairly clearly that some Samsung 13 devices just can't show Toasts.  For the record, the relevant code has migrated quite a bit, and is now:

http://dxr.mozilla.org/mozilla-central/source/mobile/android/base/home/HomeFragment.java#394

It's just showing a toast.  Other than using our own toast mechanism and/or catching exceptions (!) there's nothing to be done.  Broke devices are broke.

Comment 6

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Nick Alexander :nalexander from comment #5)
> It's just showing a toast.  Other than using our own toast mechanism and/or
> catching exceptions (!) there's nothing to be done.  Broke devices are broke.

Do you think catching exceptions is wrong here (if we break down the models as much as possible, e.g. API == 13 - maybe a model ID or similar?)? Seems better than stranding users.

Comment 7

[Nick Alexander :nalexander [he/him]]

(In reply to Michael Comella (:mcomella) from comment #6)
> (In reply to Nick Alexander :nalexander from comment #5)
> > It's just showing a toast.  Other than using our own toast mechanism and/or
> > catching exceptions (!) there's nothing to be done.  Broke devices are broke.
> 
> Do you think catching exceptions is wrong here (if we break down the models
> as much as possible, e.g. API == 13 - maybe a model ID or similar?)? Seems
> better than stranding users.

I'm cool to just catch exceptions.  The thing is that we show toasts /a lot/, and we'd need to move all toasts to the freshly wrapped helper.  That sucks, and will require some education (on the mailing list, I guess).  But we can definitely do it.

Comment 8

[Brian Nicholson (:bnicholson)]

Going to assume this was fixed by bug 1067429 unless someone can link to crash reports proving otherwise.