Re: Definition of NetBSD users

["Martin S. Weber" <Ephaeton%gmx.net@localhost>]

On Tue, Apr 06, 2010 at 01:40:05AM +0200, Martin Husemann wrote:
> On Mon, Apr 05, 2010 at 02:54:41PM -0700, Aaron J. Grier wrote:
> > I haven't had a native compiled firefox work reliably in 3+ years (they
> > appear to hang up in domain resolution after a few minutes)
> 
> Is there a PR? How can I reproduce the problem?

It's hard to reproduce if you don't have a stubborn setup. I've experienced
this a lot, too. The problem was introduced with the support of the 
multi-threaded
DNS resolving (either in base or in ffox or both) [yeah you can stop laughing 
now].

Necessary ingredients seem to be a stubborn router (on your end). It seems 
easiest
to reproduce if you create a bookmark folder with 15-25 links (like my 
"breakfast"
folder) and middle-click that one (i.e. load all of them at once).

From time to time DNS will then stall, all tabs will stop resolving. After the
default time-out, you need to reload once or twice, per tab (not all, that 
wouldn't
work), and as soon as the first DNS gets resolved again, you're fine for the 
time
being.

I have to admit, the router behind which I am sitting currently does not expose
this behaviour, nor have I ever tried to tap the network to see what's really
going on (which, I believe, would be necessary to find out where the breakage
is coming from).

I don't believe solely netbsd (or firefox) to be at fault here.

IIRC though, if firefox was in that state, you couldn't resolve hosts on the
command line either (neither via host/ping nor e.g. ssh), but I may be 
remembering
this incorrectly.

Sorry for not having PR'd this as I had the chance (i.e. the flaky hardware?),
but then again, it wouldn't have been the first PR I opened which had to be
closed years later because I no longer have access to involved hardware...

Regards,

-Martin