Firefox for Android Support Forum

So the problem is most prevalent on YouTube but other sites as well. I'll click full screen on a video and it'll look like it's going to maximize the video but then it boots me back to the home screen. I have to click on Firefox again and get the page pulled up again and then click full screen and it usually works. Sometimes I have to cycle through this once or twice

Hi support team,

I was using Mozilla Firefox on my Samsung Galaxy s20+ without any issues. I have transferred all data from my old one to new one, Samsung Galaxy S24 after this migration Mozilla Firefox crashes, when I was forwarded from an app.

Standard browser: Mozilla Firefox I have already reinstalled the Mozilla. This action works properly with other browsers.

Kind regards Mustafa

Sometimes whenever i use twitter it will crash and stop working everytime i switch a other tab it glitches and stays on the tab i switched from, and it would also black out and make the tab unusable.

Constantly crashes with the latest 3 updates. Not sure if it's on your end or the providing web sites not knowinghow to program for Android phones.

    Too many non standard screen resolutions out there for each phone???

Guesses...???

For months now, Firefox Mobile has constantly been getting "app has stopped responding" crashes and even hard crashes (multiple times per day) for Pixel users. There's already a bug report about it but the FF team's response is that they aren't going to do anything. They claim it's an issue with the kernel but no other apps / browsers on the Pixel have this problem.

This is beyond pathetic. Maybe this not-my-problem mentality is why Firefox has reduced to less than 1% penetration.

Hello,

I am getting a frequent freeze in the Android app and then shortly after a crash. Info: - happens on FF, FF Beta, and FF Nightly,and reinstall/phone reset didn't fix. - Samsung Galaxy SM-G965U running Android 10. - every error starts with java.lang.OutofMemoryError. - it never happens just on startup, just on auto fill, or some of the similar crash reports I've seen around here. - it does appear to be site-specific, but sometimes the site works and sometimes it does not: if I close the last tab after a crash, it will usually work for awhile. - Sync and disabling Add-ons doesnt fix it, although perhaps its worse with uBlock Origin enabled (not conclusively)

Thanks for any suggestions.

edited for clarity

Poco F2 Pro is hard crashing requiring device reboot, starting maybe a week ago, and has happened three times. I don't know if it's hardware related but I've not seen the behaviour in other apps. I'm not using beta version.

Very often when clicming the adress bar (almost always on sites like old.reddit.com, the app just stops responding and I must reopen it. I'd like a solution that won't involve removing all my bookmarks, history and saved data.

Dear Concern, Suddenly I Found Crashing Problem In Fire Fox New Updated Version. When I Try to Save Any Image Or Download Any File From it’s show A Crashing Problem. I attached A Photo Of This Crashing Problem. Sir Please Fix The Problem As Soon As Possible. Thank You.

I am posting this issue at the request of E from Firefox's app developer feedback after I submitted an app review.

The app continues to be unstable on my Pixel 6a (latest OS, Android 13) after freezing up on what appears to be any heavily scrolled pages or those that create a heavy cache. This freezing then causes abrupt phone restarts shortly thereafter, but not always immediately. Usually the culprit seems to be linked to Facebook album viewing, Imgur albums with article-length descriptions, etc. The abrupt phone restarting occurs whether force stopping Firefox and clearing the cache right away or not (although the restarts seem to happen faster if I force stop the app). I have simply closed the app during the freeze, put my phone down, and come back minutes or hours later to it having restarted on its own.

In addition, open tabs have a tendency to lose their scroll spots on a non-infinitely-scrolling page (e.g. an article not requiring expanding) when the app is minimized but not closed. This is probably unrelated(?) and isn't as critical as the spontaneous restarts, however.

It looks like many Pixel 6a users have had this issue, although those support threads from 8-9 months ago have now been archived. Someone else mentioned scripts from the websites themselves may be to blame? Would be curious to hear of any specific fixes. Thanks!

Frequently crashes without warning, pages lag constantly where scrolling down is impossible, even after the page is refreshed. Creates way too many new tabs (like 50 a day) and ads mess up the design of the webpage.

When attempting to enter full screen mode on Firefox for Android, and to get into landscape mode, the browser appears to crash, keeps audio playing, and "entering full screen mode" dialogue pops up. Have to open Firefox again, and can only be viewed in landscape mode while session is continued. To return to non-landscape mode, the app needs to be force stopped, otherwise you only get to see the left one third side of any web page you navigate to. Seems to have started with most recent update. Is there any way to fix?

Just updated to latest version of Firefox for Android (ver 113). When I try to watch a YouTube video in full screen, the app suddenly closes, as if I pressed the home button (note: I say "close" rather than "crash" because when I reopen it, all the pages are still loaded). This doesn't happen every time, but it is annoying. Is there any way to fix this?

When reading the site https://hellasjournal.com after a while Firefox freezes and crashes. It's not a site problem because with Chrome works fine.

My phone is on Android 13 with the latest Firefox update. Under "Crashes" in Settings, there isn't much.

Here's a video: https://imgur.com/a/7etdWuL

So on my main firefox account the app crashes after a few mins consistently, on my phone and Tablet.

However I recently made a different account using a different email adress and zero crashes.

Is it likely to be a settings issue?