undefined | Better HN

0 pointsJohnBooty2y ago0 comments

I wonder what happens if you launch FF with your wifi disabled and/or the cable unplugged?

On MacOS and Windows (I can try this on PopOS as well if you like) FF launches instantly with no complaints if the network is down. Which tells me that FF seems to properly handle situations where things are merely unreachable.

The fact that it's hanging for you implies to me that perhaps FF is getting some kind of malformed response from... something on your network. A firewall, a proxy, I don't know.

    I've not tried with those machines on a different 
    network. I assume it's related to networking in some 
    way. My network is more complex than most.

I don't know if you're open to feedback on this or not, but it feels disingenuous to state "Firefox is unusably slow" without noting that it appears to be some specific interaction between Firefox and your network. If it is a network issue, it certainly sounds like it is something FF should handle more gracefully/informatively, but that is a different matter from "Firefox unusably slow."

0 comments

JohnFen2y ago

> it feels disingenuous to state "Firefox is unusably slow" without noting that it appears to be some specific interaction between Firefox and your network.

I don't think it's disingenuous because it's only Firefox that has this issue. Every other browser is fine.

I think there's an edge-condition bug in Firefox that I'm triggering that causes this. I've spent quite a while trying to work this out before giving up entirely. However -- since it's really not at all hard to find people who have performance problems with Firefox generally, there is something going on with it. And it's something that (based on interactions with the dev team) Mozilla seems not willing to worry much about.

All that said, I try very hard to be fair to Mozilla and Firefox, in part because I've been a huge backer of Firefox since the very beginning, and still care.

j / k navigate · click thread line to collapse