Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox crashes repeatedly, on multiple devices

  • 7 odgovori
  • 1 ima ovaj problem
  • 293 views
  • Posljednji odgovor poslao Shinobi

more options

So usually ill be playing a youtube video, and eventually the frames will stop and then firefox will crash, with the

Sorry Firefox crashed error

Now i just got a new Tablet my partner was using with no crashes and im crashing on that too, so it could be an account issue?

Already tried clearing cache and data and having no Addons Any help would be appreciated :)

So usually ill be playing a youtube video, and eventually the frames will stop and then firefox will crash, with the Sorry Firefox crashed error Now i just got a new Tablet my partner was using with no crashes and im crashing on that too, so it could be an account issue? Already tried clearing cache and data and having no Addons Any help would be appreciated :)

Izabrano rješenje

Please can you paste the URL of the crash report and not the report itself.

Pročitajte ovaj odgovor sa objašnjenjem 👍 0

All Replies (7)

more options

Hi

I am sorry to hear that Firefox for Android is crashing. I hope that we can help resolve this for you. Before following the steps below, please make sure that you have updated both your Android device and Firefox for Android to the latest versions available.

As a first step, close down many of the tabs that you have open to as few as possible. Does this help reduce the incidence of a crash?

If this does not resolve the issue, open the Android Settings app, select Applications then find Firefox in the list. In the section headed "Storage", selct the option to clear the cache (do not clear data!). Does this help?

Failing that, our developers will need to look into this in more detail with some logs from inside your copy of Firefox for Android. Type about:crashes in the address bar which will display information about recent crashes. If you select the most recent "Socorro" link, a crash report will open in a new tab. If you could copy and paste the address of the page that opens into a reply to this thread, we will be able to look into this further for you.

I hope that this helps.

more options

9912eec9-7c49-494a-a934-b7e70da8bdba java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 2455832 free bytes and 2398KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.


java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 2455832 free bytes and 2398KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC. at android.view.DisplayEventReceiver.dispatchVsync(DisplayEventReceiver.java:260) at android.os.MessageQueue.nativePollOnce(Native Method) at android.os.MessageQueue.next(MessageQueue.java:335) at android.os.Looper.loopOnce(Looper.java:186) at android.os.Looper.loop(Looper.java:313) at android.app.ActivityThread.main(ActivityThread.java:8855) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

---Here is the latest crash from my tablet

more options

64cd06fb-8d89-4057-9075-e6816b2d3434 java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 1325240 free bytes and 1294KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.


java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 1325240 free bytes and 1294KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC. at android.os.ThreadLocalWorkSource.setUid(ThreadLocalWorkSource.java:68) at android.os.Binder.execTransact(Binder.java:1278)

---And here from my phone, both seem to be memory issues oddly enoug

more options

Odabrano rješenje

Please can you paste the URL of the crash report and not the report itself.

more options
more options

This seems to be the only socorro generated link

more options

Any updates on this :)