Chrome Version: ToT
Network info: Especially important on slow networks.

Steps To Reproduce:
1. Create a big file (about 500MB) and a small image file on Drive.
2. chrome://drive-internals and click "Clear local data"
3. Drag-drop the bigger file to Downloads.
4. While the copy is in progress ("syncing <filename> ..." message in Files app), open the image file from the Files app.

Expected Result:
The small image file opens asap, especially if user is seeing the app foreground.
If user goes back to the Files app, it's probably better to prioritize copying of the large file, but this is not obvious.

Actual Result:
The image file is not loaded while the larger file is downloading.
In the meantime the app shows loading progress animation.

This is caused because the both download jobs are queued with the same priority (0), and queue preemption will not happen.

If the larger file is a ZIP file (or most file types opened by an app), same thing happens by opening it instead of copying at step 3.

This can be reproduced deterministically.

What is the impact to the user, and is there a workaround? If so, what is
it?
The file still loads after a long time.
However, since not all transactions are initiated by user (e.g. when creating a large zip file on Drive, it starts uploading automatically), it can be confusing.
 

Split from Issue 810603.
Chrome Version: ToT
Network info: Especially important on slow networks.

Steps To Reproduce:
1. Create a big file (about 500MB) and a small image file on Drive.
2. chrome://drive-internals and click "Clear local data"
3. Drag-drop the bigger file to Downloads.
4. While the copy is in progress ("syncing <filename> ..." message in Files app), open the image file from the Files app.

Expected Result:
The small image file opens asap, especially if user is seeing the app foreground.
If user goes back to the Files app, it's probably better to prioritize copying of the large file, but this is not obvious.

Actual Result:
The image file is not loaded while the larger file is downloading.
In the meantime the app shows loading progress animation.

This is caused because the both download jobs are queued with the same priority (0), and queue preemption will not happen.

If the larger file is a ZIP file (or most file types opened by an app), same thing happens by opening it instead of copying at step 3.

This can be reproduced deterministically.

What is the impact to the user, and is there a workaround? If so, what is
it?
The file still loads after a long time.
However, since not all transactions are initiated by user (e.g. when creating a large zip file on Drive, it starts uploading automatically), it can be confusing.