@patrickdrd: Are there any particular steps to reproduce the issue? If so please provide screencast of the issue along with device details. This would help in further triaging of the issue.

Thanks! 

I don't know how/think you can reproduce it, 
I don't know if it's a known bug either,
but I searched in google and I didn't find anything interesting about it,
all I know is that I started chrome again right now and I got 150 lines of this message, maybe it's not actually a bug, but I need support/troubleshooting, 
what can I do to get rid of it?
I'm a developer too, but I cannot understand why this happens, what does "Cache is not initialized" mean? what cache does it need?
I even cleaned cache and the same result.

I've attached my logcat part when chrome is starting up,
133 lines with the above message!!!
can you forward it to a developer to tell me what's wrong?

Deleted: 2018-11-26-11-12-37.txt 48.4 KB

2018-11-26-11-12-37.txt 48.4 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

AFAICT in_progress_cache_impl.cc comes from the download subsystem and does not involved cache_storage:

https://chromium.googlesource.com/chromium/src/+/3ec126aa50c7bdbbfa3aa03f539f4de0cf9eace8/components/download/downloader/in_progress/in_progress_cache_impl.cc

ok, I've just checked my other two devices and it does it in them too!
one is also nougat, not rooted, stock rom etc
and the other lollipop 5.1 with microg

Seeing recent changes in https://chromium.googlesource.com/chromium/src/+/3ec126aa50c7bdbbfa3aa03f539f4de0cf9eace8 made by xingliu@.

@ xingliu: Could you please help in triaging this, please feel free to re-assign if this has nothing to do with your change.

Thanks!

I uninstalled chrome and I tried with a new, clean install,
without restoring anything, neither logging in my account,
same result..

so, maybe it's a bug after all?

We are recently changing this, in_progress_cache_impl.cc used to have bugs. +qinmin@ to this bug.

I have seen those too before. The issue is that on startup, Chrome will load all the downloads history from the history DB, and apply some of the information from the in-progress cache. However, there is no guarantee in-progress cache will be loaded before history DB. Thus causing the error in LOG.

The error can be ignored though. in-progress cache contains some information for resuming the download if it is not complete, along with some metrics for reporting. Under most use cases, these information is not needed or the information is simply empty, so you can simply ignore these logcat. We have deprecated the in-progress cache in M71, and the new proto database should fix the initialization ordering issue.