This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looking at the metrics today:
https://uma.googleplex.com/p/chrome/timeline_v2/?sid=62a6b5e55f2b83ac38e614737654f5b2

Interestingly, Chrome OS's failure rate is much higher than the others at around a 0.2%-0.5% failure rate. I wonder if this could be related to the Chrome OS only crash at issue 586836.

So reasons it can fail (I think this would always be the simple backend for this, especially for ChromeOS?):

1) The cache directory passed in doesn't exist and it can't base::CreateDirectory it.

2) File format version upgrade failures (including some kinds of trouble with the 'index' file in the directory). Actually, I am wondering about these --- who is supposed to recover from these?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Seems to me that the magnitude matches LevelDB failures -- LevelDBEnv.IDB.IOError

Going to close this as wanderview@ will be looking at all the metrics while redoing the backend.