I had a look and couldn't find any UI errors that would explain such behaviour. :-(

I had investigated this before and had merged an speculative fix (based on crbug.com/893161), all these reports seem to include this fix. :-/

A common factor is that all reports have ARC++ enabled and in the screenshot (when provided), there isn't any media Android files, Drive or Downloads.

Another M71 report - https://listnr.corp.google.com/report/85839925134

More feedback - https://listnr.corp.google.com/report/85826149681

A FilesApp foreground / background page console.log might be good to capture if we can get a reproduction from somewhere/someone -- feedback reports don't have them.

M71 - https://listnr.corp.google.com/report/85883248810

In my experience, it happens the first time I open the file browser after a reboot.  The folders show up eventually (after several minutes).

Thanks. If you know how to inspect filesApp using chrome developer tools, it would nice to capture the console log.

+sammc, any reason Downloads or DriveFS would take so long?