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

  • taaz@biglemmowski.win
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    7 months ago

    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.

    • rcbrk@lemmy.ml
      link
      fedilink
      English
      arrow-up
      11
      ·
      7 months ago

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

  • Dave@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    7 months ago

    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 :)

    • PM_Your_Nudes_Please@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      7 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.

  • draughtcyclist@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    7 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.

  • lemmyvore@feddit.nl
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    7 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.