Sure. I've got a lot on my plate, but probably not as much as Shaver (I didn't even know he fixed bugs...)
I haven't had time to look over the 186 comments, but the first thing that comes to mind is that multi-process (electrolysis) may make this bug moot, assuming that DNS lookup occurs in the subprocess and not in the chrome process. Does anyone have a sense if that is correct? If so, unless we're very close to a architecturally clean fix here, it may make sense to wait and get this "for free" and "right way" later.
> Jason can you take ownership of this bug?
Sure. I've got a lot on my plate, but probably not as much as Shaver (I didn't even know he fixed bugs...)
I haven't had time to look over the 186 comments, but the first thing that comes to mind is that multi-process (electrolysis) may make this bug moot, assuming that DNS lookup occurs in the subprocess and not in the chrome process. Does anyone have a sense if that is correct? If so, unless we're very close to a architecturally clean fix here, it may make sense to wait and get this "for free" and "right way" later.