Issue metadata
Sign in to add a comment
|
Opening a zip from Google Drive gets Files app stuck and can't eject |
||||||||||||||||||||||||
Issue descriptionM55 | Samus | 8872.19.0 55.0.2883.22 1. Open Files app 2. Go to Google Drive 3. Double click an 80MB zip file with some pictures 4. After a while it will show a notification "An operation is taking longer than expected. Do you want to abort it?" 5. Press Abort 6. Go to eject the zip from the files app 7. Get a notification "Don't remove your device just yet" A few seconds later the Abort notification appears again This notification keeps appearing no matter no how many times I press abort and I can't eject the zip from files app either.
,
Nov 21 2016
I have encountered a similar bug on Acer CB3-111 running ChromeOS 54.0.2840.93, Platform version 8743.83.0 (Official Build) stable-channel gnawty. It can be easily reproduced with the following steps: 1. Take 10-15 random picture files or just take some screenshots 2. Zip them using the built-in Chromebook zip app 3. Do not mount the zip file 4. Upload the zip file to Google Drive 5. Restart the Chromebook or logout and login 6. Download the zip file from GD by checking the "available offline" option 7. Open the zip file _not_ from the "Downloads" folder, but from the "Offline" folder 8. The ZIP Unpacker extension crashes, not rendering the thumbnails of the picture files and displaying a loop of "The operation is taking longer than usual. Do you want to abort it?" error messages. Clicking "Abort" does not help, the archive cannot be unmounted and the pictures cannot be displayed. I have included screenshots depicting the bug. It can be reproduced on a freshly powerwashed machine with all extensions disabled, and the file in question does not contain any special characters. Could anyone tell me if a bug like this affects only the user profile on which it occurs, or can it also affect other users or the Guest Mode? Can it cause some kind of file/cache corruption or is it just a minor nuisance?
,
Dec 1 2016
This issue should happen only when the Drive's download queue is full. Then the ZIP unpacker extension would be stuck in the queue, which would cause showing the notification about the operation taking long time. It's not ideal, but this shouldn't happen often. If it happens again, you can check the queue status in chrome://drive-internals. Once the other tasks in the queue are processed, the ZIP should finally open. Another reason for this issue could be a very slow or unreliable Internet connection. In either case we should let the user unload the ZIP file. Also, aborting should unload the file as well.
,
Dec 8 2016
,
Jan 14 2017
Tomasz, Thank you for replying. However, I believe that your diagnosis might not be correct. I have reproduced the bug today on the newest stable ChromeOS build [55.0.2883.105 (64-bit) Platform 8872.76.0 (Official Build) stable-channel gnawtyand] and noticed that when the bug occured, the Drive Internals "In-flight Operations" list was empty. I have attached a screenshot. I tried waiting for about 25 minutes but the ZIP did not open and was frozen in the "operation is taking longer than expected" state. The only way to make the problem go away was by logging out of my profile and logging in again. The one thing that concerns me is the Image Loader extension console log. When the bug occurs, it shows a 404 error. I have also noticed that when the zip file works correctly, the Image Loader extension soon disappears from the Task Manager, but when the bug occurs it would stay there forever. Maybe therein lies the cause of the problem?
,
Jan 27 2017
Thanks for the investigation. Could you confirm what version of the ZIP unpacker you have? You can do it by executing the following line in dev tools for the ZIP unpacker extension: > chrome.runtime.getManifest().version Also, did the issue keep reproducing recently?
,
Feb 1 2017
This appears to be an old problem which still exists on my Asus Flip 55.0.2883.105 Tries to mount zip file (32 Meg 30 photos) but hangs up and can't unmount or abort
,
Feb 5 2017
Tomasz, According to the manifest, my ZIP Unpacker version is 0.76. From my experience the problem seems to occur only the first time you open a given file directly from Google Drive (i.e. not from the Downloads folder) and is difficult to reproduce once the bug occurs once for that file. It will recur only after a powerwash. Let me give you an example. Let'a say we have two zip files on Drive named file1.zip and file2.zip. We open file1.zip following the steps from comment #2 and the bug occurs. Then we logout and login or restart the Chromebook and the file opens correctly. From now on, the bug becomes nearly impossible to reproduce for file1.zip, even after clearing the Drive internal cache, and will reproduce only after powerwashing the machine. However the same bug will occur without powerwashing the first time you open file2.zip and will also disappear for this file after occurring once and until the next powerwash. I hope that my explanation is sufficient but I will be happy to clarify further if needed.
,
Dec 8 2017
,
Dec 8 2017
Reassigning to yamaguchi@ as it might have been fixed recently.
,
Dec 11 2017
I think this has been fixed as Issue 457448 , and should be fixed by now. If it is not the case, feel free to reopen. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by weifangsun@chromium.org
, Nov 15 2016Cc: -weifangsun@chromium.org
Owner: weifangsun@chromium.org
Status: Assigned (was: Untriaged)