this post was submitted on 31 Aug 2026
879 points (99.5% liked)
Technology
87744 readers
4340 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No, that issue definitely occurs in Firefox Android sometimes. The tab just gets stuck and does nothing. Has been happening for years, in fact, so it's not something new. Might be due to some specific settings, but I like my settings and the problem doesn't pop up too often, so eh.
Desktop Firefox also gets this sometimes, actually. The tab just doesn't load until I bash ‘enter’ on the address bar, or create a new tab. Since afaik Firefox uses its Gecko engine on both platforms, the issue could be in the engine rather than the UI.
Honestly I didn't recall anything where things are stuck.
Are you sure that the issue on Android isn't caused by closing a link and the app opening Firefox in its context?
If this is such a percentage issue I'd there big open about it?
It happens within Firefox, without rhyme or reason that I could discern. I think it's more common if I open a link from another app, then switch away from Firefox while the page loads in the background; or when returning to FF and it tries to reload a previously suspended tab. Firefox is allowed to load stuff on my phone in the background even when battery saving is on (which it always is), but I guess FF might get into a fight with the system over available memory, with the system killing one of FF's processes/threads. Wouldn't explain it happening on the desktop, though.
It happens pretty rarely for me, and I have no idea how it could be reproduced. So, I already barely ever open issues (by principle), and certainly won't report this. Idk about others — wouldn't be surprised if there's a bug about this among the many thousands of issues that Mozilla has.