New issue
Advanced search Search tips

Issue 777757 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Opening a zip file being created shows error message telling the zip file is broken

Project Member Reported by yamaguchi@chromium.org, Oct 24 2017

Issue description

Chrome Version: 63.0.3239.7

What steps will reproduce the problem?
(1) Put about 800 photo files in a directory. Those files can be copies of a single image file.
(2) Select the directory, right-click and choose "zip selection".
(3) Double-click the new zip file while a notification like [zipping 800 files...] is shown on the bottom-left of the Files app window.

What is the expected result?
mount the zip file and show partial file list already compressed, or
wait until the zip file becomes readable.

What happens instead?
Error appears in the system notification.
---
ZIP unpacker
Archive.zip
The archive format is not supported, or the file is broken.
---


Workaround

Wait until "zipping..." message disappears and double-click the new zip file again.
Once the compression is finished, it should successfully mount the zip file.
 
zip-in-progress-error.png
36.4 KB View Download

Comment 2 by sashab@chromium.org, Feb 22 2018

Labels: CrOS-FilesApp-Zip

Comment 3 by sashab@chromium.org, Feb 28 2018

Labels: -CrOS-FilesApp-Zip CrOSFilesFeature-Zip
Status: Available (was: Untriaged)
Postpone until launch of zip archiver to confirm.
Status: WontFix (was: Available)
This is a problem for all file formats, not just zip. Until the file is fully written, it isn't valid, so any program trying to open it will fail. For zip in particular, the file index is written at the end of the file, so there's no way to show partial results.

The only possible solutions are to either prevent the user from accessing a file that is being created, or wait for the operation to finish and then open it. But since this is a general problem that would affect any chrome app that creates files, I don't think we should be doing anything specific for zip.

Without a general solution for all chrome apps, I believe the current behaviour is the correct one. The file is broken until the zip operation is done.

Sign in to add a comment