Has anyone experienced this? Using my mom's comcast wifi when I navigate to a new site the navigation takes a very long time, like a full minute. Once it eventually completes, I can click around inside the site at normal speed. This only happens with Firefox (I tried installing the Duckduckgo browser and it doesn't have the problem). It only happens on the comcast wifi (switching to mobile internet makes it go away). Using my laptop on the same wifi network has no problem. The issue on Android only started with the last update on F-droid. The only extension installed is ublock origin.
I can make some useless guesses at what might be happening (DNS queries getting hung somehow) but haven't made any attempt to check them with network sniffing.
Has anyone else experienced this?
17 Comments
ozymandias117@lemmy.world · 11 pts · 1y
I'm seeing what sounds like the same issue.
Based off your comment on extensions, I just disabled all extensions, and the problem went away.
If I enable any extension, it breaks again...
So to me it seems like a bug with the extension system
Edit: tested with Privacy Badger, uBlock Origin, and NoScript
Edit2: Fennec F-Droid build #1420020; Android 16 (GrapheneOS 2025081400)
Edit3: Found a bug report about it: https://gitlab.com/relan/fennecbuild/-/issues/134
xmanmonk@lemmy.sdf.org · 7 pts · 1y
Experiencing the same with Fennec.
ozymandias117@lemmy.world · 4 pts · 1y
Looks like a reported issue
https://gitlab.com/relan/fennecbuild/-/issues/134
styanax@lemmy.world · 2 pts · 1y
ozymandias117@lemmy.world · 1 pts · 1y
I switched to quad9 private DNS and turned private DNS off, both in a private tab of Fennec - same results
kaidenshi@lemmy.world · 7 pts · 1y
I'm having the same issue with Fennec from F-Droid on a Pixel 8 Pro. I thought it was network issues but it happens no matter how I'm connected, WiFi or 5G. Chrome doesn't have the issue on the same phone and all apps work fine so it's definitely a Firefox engine issue.
ozymandias117@lemmy.world · 4 pts · 1y
It sounds Fennec F-Droid specific, somehow.
Reports here are saying the official Firefox build works fine: https://gitlab.com/relan/fennecbuild/-/issues/134
It also seems to affect certain extensions
Ghoelian@lemmy.dbzer0.com · 6 pts · 1y
I'm not seeing this problem on the latest ironfox. Even heavier sites like github load within a few seconds.
LiveLM@lemmy.zip · 4 pts · 1y
On the latest F-droid blog post they listed this as a known issue:
Brewchin@lemmy.world · 3 pts · 1y
My two thoughts on this are DNS, too:
But as you've tried DDG browser without issues, it's more likely to be the first option.
Also, any VPN you may be using.
solrize@lemmy.ml · 3 pts · 1y
Thanks. The browser doesn't have an HTTP over DNS setting afaict. It doesn't have nearly as many configuration options as desktop firefox.
Brewchin@lemmy.world · 2 pts · 1y
Can't speak to Firefox on mobile, as I switched to Waterfox some time ago, but the latter definitely has it.
Oh well. I wish you the best in working it out.
solrize@lemmy.ml · 3 pts · 1y
Yeah that is not there on the Fennec that i'm using. But, there is a long gitlab thread someone linked to, that discusses what's going on. With luck there will be some kind of fix and meanwhile there are some workarounds.
ilillilillilillililli@lemmy.world · 3 pts · 1y
It seems likes a Fennec and Firefox specific issue. Try Ironfox and see if it behaves differently. Its not on F-Droid. Obtanium is the easiest way to install Ironfox (and keep it updated).
danglybits27@sh.itjust.works · 5 pts · 1y
There actually is an F-Droid repo now for Ironfox, which I think I accidentally found in the repo list of NeoStore (another F-Droid client.) Link is also on gitlab:
https://gitlab.com/ironfox-oss/IronFox https://fdroid.ironfoxoss.org/fdroid/repo/index.html
ilillilillilillililli@lemmy.world · 2 pts · 1y
Oh, no shit! Now I know. I appreciate that!
zer0bitz@lemmy.world · 2 pts · 1y
Xiaomi 11T Pro and Fennec from F-Droid with uBlock Origin, Privacy Badger and Consent-O-Matic browser addons. Thought it was my DNS because I replaced my router last weekend. Im glad that I found this post.
limerod@reddthat.com · 1 pts · 1y
Yes, its a known issue since v142.0. You will have to wait or try workarounds to get around this issue.