Did any notification message appear in the notification area of the Files app, or in the system notification when this happened?
For example:
- scanning file
- syncing file
- already mounted
- file is broken

Also, will you copy and paste error messages in the developer tools Console by
chrome://inspect/#extensions and opening the [inspect] of Zip Archiver, if it's on a dev device?

Hi @yamaguchi, there was not any notification appearing in Files app and neither any system notification. 

By going to developer tools Console, I didn't see any error messages of Zip Archiver. But I did see error messages of Files app. Attaching log file for this.
Thank you!

Deleted: Files_error.log 12.8 KB

Files_error.log 12.8 KB View Download

I think this is exactly the same issue as Issue 799642, where the extension fails at the startup in both purpose.

Can you verify these things?
- if it happened on Google official build (as opposed to Developer build)
- if it happens both with #zip-archiver-unpacker flag Disabled and Enabled

When #zip-archiver-unpacker flag is disabled as well as when enabled, on official live dev build M65 10278.0.0, 65.0.3299.0
-- caroline: zip file didn't open
-- link, kevin, cave and coral astronaut: I was able to open zip file and it got mounted.

Merging to Issue 799642 as this is technically identical issue to that, and I had left some test logs there.

Both the ZIP unpacker and Zip Archiver extensions are failing to start due to pNaCl translator error, only on the image built on the official builds for caroline.