Spike in FILE_NOT_FOUND in Net.ErrorCodesForMainFrame3 on Android Canary/Dev |
|||||
Issue descriptionRef: https://uma.googleplex.com/timeline_v2?sid=6a1b6671f77cbeb82e2ae3283bce4eb3 Seems to happen in roughly 66.0.3335 in Canary, and around 66.0.3343.0 in Dev (which is the first dev build since 3325)
,
Feb 28 2018
Trending down as of 02/26.
,
Mar 23 2018
This is propagated to Beta and looks real： https://uma.googleplex.com/timeline_v2?sid=28e445e27880a512fecc71841fd170db. Looks like it's correlated with version release. Might be 3333.0 to 3334.0.
,
Apr 17 2018
Still going. Regression range looks like 3335.0 - 3336.4 to me: https://uma.googleplex.com/timeline_v2?sid=f255c9b9c88440cd6d060040ca77469a Range: https://chromium.googlesource.com/chromium/src/+log/66.0.3335.0..66.0.3336.0?pretty=fuller&n=10000 Suspecting r533340, mek can you verify that failed blobs can return FILE_NOT_FOUND? If so, this is probably WAI.
,
Apr 17 2018
Yeah, reading blobs can return FILE_NOT_FOUND, and in particular will fail with FILE_NOT_FOUND if the blob url isn't valid/isn't mapped to a blob. So this does indeed sound WAI.
,
Apr 25 2018
Issue 824993 has been merged into this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by morlovich@chromium.org
, Feb 15 2018