firefox hangs browsing theguardian.com and opening background tabs
Categories
(Firefox for Android :: Tabs, defect)
Tracking
()
People
(Reporter: giunta.gaetano, Unassigned)
References
Details
Firefox for Android
Steps to reproduce:
Browse theguardian.com website.
From the homepage, select multiple articles to "open link in new tab" for reading later, one by one, while scrolling down the page
Actual results:
At some point, but generally before having opened in the background half a dozen tabs with new articles, the browser more or less locks up.
The symptoms are:
- if you scroll down further the homepage, the part which had not yet been shown on screen is blank, ie. the page looks truncated
- going to the tab list, the previews for the other tabs which are opened on the guardian website articles pages are all blank
- the browser is extremely slow and unresponsive
- also, android becomes sluggish and unresponsive
This situation tends to persist for a while. It might be that it would resolve by itself if I waited long enough, but I almost never wait for it to sort itself out.
The way to fix it is to simply stop and restart firefox.
After restarting it, the browser is responsive. Going to the tab list, and switching to the tabs which are loading the article pages does work.
Expected results:
This happens in firefox for android. It has been going on for a while, so across multiple versions. Tested using different Samsung galaxy phones and Android versions. I do have uBlock origin installed.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Tabs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
TLDR: The most simple mitigation: ** If you do "Reject All“ in "Manage or reject cookies" , the site becomes normal. **
| Reporter | ||
Comment 3•1 year ago
|
||
Thanks @jackyzy823 - the suggested workaround does seem to work!
I had never tried that because I do have a Guardian subscription, and thought that being logged in and rejecting all cookies at the same time would not work (and being logged in prevents the annoying "please subscribe" popup from appearing). But it seems that it is ok, so i am a happy camper.
I am not 100% sure if I should ask for a bit more detail on the underlying technical issue (I presume there is some nasty js/network/css/cache interaction problem deep down somewhere) or just forget about this forever :-D
Comment 4•1 year ago
•
|
||
Tech details are in the comment 9 of the bug 1788530 and the following replies.
Basically it is a division by zero bug.
| Reporter | ||
Comment 5•1 year ago
|
||
Thx for the info. Closing this one as duplicate
Description
•