Matthew Dillon wrote: But what changed recently to cause this to start happening? Presumably one of the libc commits? -Matt This has always been a problem with Mozilla. They use a threaded resolver code path which tiggers this problem on all of the BSDs. -DR