Fennec 142 takes several minutes to load websites, when using Ublock Origin or Privacy Badger or Ghostery

After updating to Fennec 142, sites wouldn’t load. I narrowed it down to two problematic addons: UBlock Origin and Privacy Badger. Having either one enabled causes sites to take forever to load.

I was not able to reproduce this with offical Firefox.

Also see firefox android (fennec) hangs connecting to websites for minutes since v142 after start · Issue #3770 · uBlockOrigin/uBlock-issues · GitHub

3 Likes

Fennec 142.0.0 is completely broken, none of the workarounds make any difference on my devices. Please remove it from fdroid. You knew about this for several hours now yet it’s still being served as an “update”

2 Likes

Please follow the linked issue.

We hope whatever uBlock linked issue can be found faster

It works for me after disabling RethinkDNS which btw was also upgraded recently.

Indeed RethinkDNS logs show some failed DNS requests that could be related.

Setting DNS to Google in RethinkDNS apparently helps… at least for now.

+1 for F-Droid making downgrades easier.
I know that recent Android versions are preventing “easy” downgrades but it’d be nice to be able to directly download the APK for any version from the app, so at least that step is much easier.

One more datapoint: I have the same issue on /e/OS, and for me it was mostly solved by deactivating noScript (but not by deactivating all NoScript rules). Before that, I tried quitting (with image file deletion active), but that did nothing for me. Interestingly, I seem to be able to keep uBlock running in the meantime.
=> pretty inconsistent behaviour, thus it might take a while to fix this. In the meantime, I’m happy to note that fennec has brought a nice large complement of search providers back that were removed in a previous update, without making me add them myself. Thanks!

(and as for the reason I’m posting here and not on the Fennec Gitlab: gitlab.com requires phone numbers for registration now, and I’m really not up for that)

Android has never allowed downgrades unless the app is marked debuggable or the system itself is a debug build.

1 Like

never easy to downgrade, except for rooted devices + corepatch for example
Another thing is: backup before updating… Have to say issues like this with Fennec are really unusual

I remember being able to “just downgrade”, but that may have been a LineageOS thing.

Anyway, uninstalling (while keeping user data) and then installing an older version is functionally the same thing from a user perspective, and that should always be possible. It may break things if user data format has changed, of course, but that’s a fundamental risk of downgrading, and unavoidable unless someone produces a dedicated version-specific conversion routine.

…but actually, this discussion already exists in a different thread, so let’s leave it at that. It’s just times like this (or that time when my K-9 was broken for weeks…) when it would be really handy.

Same here, latest F-Droid Fennec is very slow. Worked fine before and other browsers work fine as well. Let me know if/what detail needed. Started happening since last update and it’s unbearable slow.

142.0.0 fennec fdroid

Follow the toot or the TWIF ( Single Point Of Slowness | F-Droid - Free and Open Source Android App Repository )

/LE: fixed link

1 Like

It ain’t a typo mate. Works fine.
Else navigate from news section.

Yeah yeah typo carry on:)

1 Like

I tried few scenarios, but at the end, Fennec isn’t a usable as it is used to.

Disabling or uninstalling i.e. adblock, decentraleyes brings a temporary working again, enabling it again makes browsing work for a bit too.

But as soon you close Fennec and open again (with it enabled still), the whole slowness starts again.

Any solution insight (not workaround)?

Official Firefox doesn’t have the problem in latest version (142.0.1) - Fennec is 142.0.0.

Wonder why “close screen (lock device) then unlock” does not work for everyone

I have at least 2-3 devices, Android 14,15,11 that seem fine with this trick

Maybe accessibility settings, background settings, the launcher settings, admin access not set for launcher, and many more can be the cause.

None setup

My wallpaper?

Different ones

None setup, what has my launcher to do with locking the device by pressing the hardware power button?

:slight_smile:

For Fennec.

No, I meant app running in background, settings. I turn off this option for almost everything, if available.

Hmm

It is not just about locking with hardware button. At times, and with some devices, the moment you lock the phone, the app goes into background (do not kill), and at times that page also closes (if via a popup as a webview), that way it does not work.

I tried almost every manner, for me it works automatically at times, and at times it never loads.
So, a proper regression is needed, or multiple for that matter, & it will keep on getting frowned upon.

1 Like

After the last update, Fennec often seems to get stuck. Seems to happen mostly, or always, after changing networks, or turning Mullvad on / off. Until today, clearing history helped, but now nothing helps :frowning: I had to put the poor beast out of its misery and install Weblibre – so apropos, I welcome comments comparing the two. I can provide more info, but for now I can’t use Fennec regularly, so I may not be able to reproduce.

Almost fixed, yes :tada: