this post was submitted on 01 Jun 2024
52 points (100.0% liked)

Firefox

17880 readers
102 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

Sometimes I'll be browsing Firefox and things go wrong seemingly at random - all pages load indefinitely or show a screen indicating failure to load. This can be fixed by running pkill firefox and then starting a new instance. A look at Dev Tools shows that all requests fail and a message NS_BINDING_ABORTED is shown. I have looked up "firefox NS_BINDING_ABORTED" but none of the results 1 2 3 4 5 6 7 provided any solution.

Does anyone here know more about this issue?

Firefox version information:

Firefox Borwser 126.0

Mozilla Firefox for Arch LInux

archlinux - 1.0

top 10 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 5 months ago

Dns issues. Had similar with pihole before I configured it correctly.

[–] [email protected] 5 points 5 months ago

Before you do anything else do a full memtest on your RAM. Bad RAM sectors can affect apps in weird, seemingly unrelated ways.

[–] [email protected] 11 points 5 months ago (1 children)

No idea if it's related, but I see similar behaviour (the not loading, rather than the error message) whenever Firefox requires a restart for an update. It doesn't make it clear this is what is happening, it just stops loading web pages in existing tabs. Only if I open a new tab does it show the "Restart to keep using" message.

I've spent far too much time diagnosing network issues without realising I just needed a restart :)

[–] [email protected] 2 points 5 months ago

Yeah, I have also experienced this. Particularly annoying when I’m at work, waiting on emails to come in. Then I realize my email has been frozen in the background for 45 minutes, because Firefox silently froze all my tabs and needs to restart for an update.

[–] [email protected] 17 points 5 months ago (1 children)

I'm going to go out on a limb and say it is DNS

[–] [email protected] 14 points 5 months ago

But it is never DNS. ^It^ ^was^ ^dns^

[–] [email protected] 7 points 5 months ago

This failure essentially means there's an issue at either the DNS or TLS layers. I'd start looking at TLS, namely trusted root certs and OpenSSL.

[–] [email protected] 21 points 5 months ago* (last edited 5 months ago) (1 children)

I don't have time to browse all the tried solutions but this happens to me when my DNS gets wonky, especially systemd-resolved with dnssec enabled sometimes just stops resolving random domains, even with allow-downgrade.

[–] [email protected] 11 points 5 months ago

Same. Otherwise it's dnscrypt on the router that's gone wonky.

[–] [email protected] 6 points 5 months ago

Have you tried a hard refresh (Ctrl+F5) when this happens?