New issue
Advanced search Search tips

Issue 721580 link

Starred by 2 users
Status: Archived
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Spike in Net.ErrorCodesForMainFrame3.NAME_NOT_RESOLVED errors. CrOS Beta

Project Member Reported by kapishnikov@chromium.org, May 11 2017 
Tracking bug to keep an eye on the spike of Net.ErrorCodesForMainFrame3.NAME_NOT_RESOLVED errors.

https://uma.googleplex.com/timeline_v2?sid=135d5e8e3cd55203d5f815e58acd49cc

Comment 1 by rsleevi@chromium.org, May 18 2017

Components: -Internals>Network Internals>Network>DNS
Owner: juliatut...@chromium.org
Julia: Any thoughts here? I see another spike happening on my triage stint, and nothing stands out as obvious. Have any experiments rolled out that you're aware of?

Comment 2 by mge...@chromium.org, May 19 2017

Owner: mge...@chromium.org
DNS stuff goes to me these days. I don't know of any experiments.

Comment 3 by mge...@chromium.org, Mar 2 2018

Owner: ----
Status: Archived (was: Untriaged)
►

Sign in to add a comment