On Sun, Feb 11, 2018 at 12:37:09PM +0100, Matthieu Herrb wrote:
> Hi,
>
> I ugraded my laptop from sources to -current yesterday. Since then
> firefox stops resolving host names after a dozen of minutes or so.
> The network.dnsCacheExpiration=0 setting mentionned by phessler on
> mastodon doesn't help.
>
> It's not the firefox port itself, since it started after I rebooted a
> the new kernel, while base and xenocara were rebuilding. My previous
> kernel was from jan, 31.
>
> Other programs are fine (including chromium), but appart may be chromium
> nothing I run is using threads and name resolution at the same time .
>
> Any idea of what's causing this, or should I start bisecting ?
>
> --
> Matthieu Herrb
There's been a commit to libc/asr, but afaik firefox does it's own resolving.
Plus what you describe suggests a kernel change.
-Otto
