I once thought this is same as Issue 797854, but turned out to be a different one.

Chrome Version: 76.0.3372.0

Steps To Reproduce:
(1) Go chrome://drive-internals.
(2) Click "Clear local data" button.
(3) Try to zip a file (about >100MB) on Drive.
(4) Observe [In-flight operations] and [Event log] in chrome://drive-internals.

Expected Result:
The zip should finish in a reasonable length of time.
The logs indicate a one-shot download of the file being zipped.

Actual Result:
The ID of the operation keeps increasing. It indicates that the download operation is intermittently cancelled and scheduled again.
The event log also indicates periodic cancellation.

FILE_QUEUE pending: 1, running: 0
2018-03-24T00:22:08.171: [info] Job started: TYPE_DOWNLOAD_FILE STATE_RUNNING [2] bytes: 0/632860544 - FILE_QUEUE pending: 0, running: 1
2018-03-24T00:22:09.007: [warning] Job done: TYPE_DOWNLOAD_FILE STATE_RUNNING [2] bytes: 525863/632860544 => DRIVE_CANCELLED (elapsed time: 835ms) - FILE_QUEUE pending: 0, running: 0
2018-03-24T00:22:09.045: [info] Job queued: TYPE_DOWNLOAD_FILE STATE_NONE [3] bytes: 0/632860544 - FILE_QUEUE pending: 1, running: 0
2018-03-24T00:22:09.045: [info] Job started: TYPE_DOWNLOAD_FILE STATE_RUNNING [3] bytes: 0/632860544 - FILE_QUEUE pending: 0, running: 1
2018-03-24T00:22:09.684: [warning] Job done: TYPE_DOWNLOAD_FILE STATE_RUNNING [3] bytes: 1048576/632860544 => DRIVE_CANCELLED (elapsed time: 639ms) - FILE_QUEUE pending: 0, running: 0

As a result, the zipping operation takes very long time (more than 10x, compared to when marking the file as 'available offline' before zipping).

This is reproduced deterministically.