Closed Bug 1090279 Opened 6 years ago Closed 1 year ago

java.lang.OutOfMemory while parsing activity intent extras

Categories

(Firefox for Android :: General, defect)

All
Android
defect
Not set

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox33 --- affected

People

(Reporter: snorp, Unassigned)

References

Details

Found on Google Play dashboard

java.lang.OutOfMemoryError
at android.util.ArrayMap.allocArrays(ArrayMap.java:197)
at android.util.ArrayMap.ensureCapacity(ArrayMap.java:307)
at android.os.Bundle.unparcel(Bundle.java:247)
at android.os.Bundle.getString(Bundle.java:1118)
at android.content.Intent.getStringExtra(Intent.java:5145)
at org.mozilla.gecko.util.StringUtils.getStringExtra(StringUtils.java:195)
at org.mozilla.gecko.GeckoApp.earlyStartJavaSampler(GeckoApp.java:1091)
at org.mozilla.gecko.GeckoApp.onCreate(GeckoApp.java:1127)
at org.mozilla.gecko.BrowserApp.onCreate(BrowserApp.java:479)
at android.app.Activity.performCreate(Activity.java:5451)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1093)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2377)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2471)
at android.app.ActivityThread.access$900(ActivityThread.java:175)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1308)
at android.os.Handler.dispatchMessage(Handler.java:102)
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)
Richard, this looks like maybe it's still some variation of the Facebook thing?
Aye, something like that. Not sure how worthwhile it is to keep whacking this mole, though.

Only one crash?
(In reply to Richard Newman [:rnewman] from comment #2)
> Aye, something like that. Not sure how worthwhile it is to keep whacking
> this mole, though.
> 
> Only one crash?

No, it's the top crasher in Google Play for this week. 77 this week, 325 total.
(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #3)
> (In reply to Richard Newman [:rnewman] from comment #2)
> > Aye, something like that. Not sure how worthwhile it is to keep whacking
> > this mole, though.
> > 
> > Only one crash?
> 
> No, it's the top crasher in Google Play for this week. 77 this week, 325
> total.

This is about the same stats I saw for the Facebook thing too. Weirdness.
*sigh*

N.B., Parcelable is very sensitive to value order. This OOM isn't due to a big parcel, it's due to the caller writing bullshit into the parcel. We can band-aid it, I guess.
Depends on: 1090385

bug 1090385 was expected to fix this one. Did it?

Flags: needinfo?(snorp)

Yeha, haven't seen this in the play store recently.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(snorp)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.