New issue
Advanced search Search tips

Issue 665191 link

Starred by 1 user
Status: WontFix
Owner:
grt@chromium.org
Closed: Jan 2018
Cc:
forshaw@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

spike in NOACCESS launch error on win10 for new Chrome version

Project Member Reported by wfh@chromium.org, Nov 14 2016 
Version: M53+
OS: Windows 10

See graph:

https://uma.googleplex.com/p/chrome/timeline_v2?sid=05620eec2252f2b366a8539b88bdb6d2

Not sure why this is happening.

Comment 1 by bsep@chromium.org, Nov 23 2016

Cc: -grt@chromium.org
Owner: grt@chromium.org
With no context this seems bad to me. Assigning to grt@, please triage or close if there's nothing to do.

Comment 2 by grt@chromium.org, Nov 28 2016 

Is it a coincidence that 54.0.2840.71 pushed to 100% of stable just before the most recent giant spike and that 53.0.2785.143 pushed to 100% of stable just before the previous one? Did something change in these releases? Could there be a problem when relaunching to pick up an update?

Comment 3 by grt@chromium.org, Apr 4 2017 

I'm not sure that there's anything to do here. NOACCESS errors spiked around Sept 17, Oct 4, and Oct 26. Since then, it's been down in the "low data volume" range. Should we close this, Will?

Comment 4 by grt@chromium.org, Jan 5 2018

Status: WontFix (was: Available)
I'll take that as a yes.
►

Sign in to add a comment