Google Drive takes a long time to show up |
|||||
Issue descriptionChrome Version: 60.0.3086.0 What steps will reproduce the problem? (1) Go through the "critical update" flow. (2) Sign in to device (3) Open files app What is the expected result? Files app opens with Google Drive shown as a root in the side panel. If there is a delay we should give the user some feedback about that. What happens instead? Files app opens but does not show Google Drive. After about 20 seconds Google Drive shows up in the side panel. See video for flow (apologies for poor quality): https://goo.gl/photos/vdVfxQTcxMFCU4nr6
,
May 3 2017
Yes, this behavior is consistent every time I sign out and back in or reboot after the update.
,
May 8 2017
I can't think of any reason off the top of my head that migration would slow things down. Can you file feedback if you haven't already and link to it here. A couple other things to check: Does this happen to new profiles that did not get migrated Does this happen on other boards with ext4-crypto Does this happen on other M60 boards without ext4-crypto
,
May 8 2017
We're adding bunch of xattrs that doesn't fit in the inode and spill into another page, so it might penalize the cold directory load case? If that's the case then we should be able to repro. Is there a way to know how many files are there in the cache directory ? It should still be possible to run Kevin custom build if things reproduce but we're introducing a large difference with M vs N stack also. nya@ could it be something related to other parts of files app integration related to Android ? Would staring at the task manager / chrome://tracing help diagnose this issue?
,
May 8 2017
We should clean up the temporary xattrs when they're no longer needed. Will file a separate bug for this.
,
May 8 2017
Filed crbug.com/719287
,
May 8 2017
yamaguchi@ is looking into this and trying to repro it. Thank you!
,
May 8 2017
I could not reproduce with 60.0.3086.0/9519.0.0 on SAMSUNG Chromebook Plus. Will you report error using alt + shift + i while the issue is happening?
,
May 9 2017
Sorry, I can't reproduce it anymore. I'm now on 60.0.3092.0/9532.0.0 Not sure if something changed, I just reset (powerwashed) the device this morning. Should I close this?
,
May 10 2017
I think we can close this issue if the original issue is not happening anymore. I think the case might be related to the network connection. We can see "My Drive" appear a few seconds after "Google Drive" volume if we connect a device to a network with narrower bandwidth and clearing the local cache at chrome://drive-internals. Though, expected behavior is that Google Drive volume and My Drive root appears soon and then its child nodes appear as it is loaded.
,
May 10 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by weifangsun@chromium.org
, May 3 2017Components: Platform>Apps>FileManager
Owner: fukino@chromium.org
Status: Assigned (was: Untriaged)