Do we have a confirmed repro? I tried a few of the ones listed in the user feedback and was not able to reproduce (55.0.2883.91 / Android 6.0.1; Nexus 7 Build/MMB29K)

I can't reproduce this issue as well but I'm reaching out to see if users can provide repro steps. Some users report this happens when they try to download large files.

Here are OS and device information: 

Android 5.0, 5.1, 6.0

Devices:
Galaxy A5(2016) 
HUAWEI G7 Plus (HWRIO)
HUAWEI Y3II (HWLUA-U6582)
Galaxy J7 (j7e3g)
Redmi 3S (land)
Galaxy A7 (a7lte)
Galaxy Note3 (hlte)
CANVAS UNITE 2 (A106)
Moto G (1st Gen) (falcon_umts)

kravula@ can you try to repro?

Tried on the below devices but issue not reproducible, File downloads 100% with out any freezing or any other issues.

Samsung J7(SM-J700F) / MMB29K
Redmi Note 3 / LMY47V (MIUI Global 8.0  8.0.6)
Micromax CANVAS UNITE 2 (A106) /5.0

Adding the downloads team to the issue.

kgnaidu@ what size download were you trying?  Feel free to bounce back to me.

It sounds like the download sits at 100% and has 0 seconds left remaining but doesn't actually finish.

Some ideas we should look into:
- Are we misrepresenting the time remaining?
- Do we have a bug in our notification/callback code to actually mark the download as done and trigger the next step in the state machine?
- Do we have any post processing going on that could take a long time when downloading is "complete" but not complete?

I think the progress and the time remaining should be correct, however, the download item is not transitioning to a Complete state.

DownloadItemImpl::IsDownloadReadyForCompletion() has some checks in it, however, none of them seems matter. For dangerous download, we don't show the notification, and not all user reports are about dangerous download.

Another possibility is there are some issues renaming the temporary file to the final target, but that is also very unlikely since Chrome should have already the temporary file before.

@ dtrainor, The downloaded file was around 150 Mb.

I am able to repro the issue which was given in user feedback reports here in the below report. 

https://hotsauce.corp.google.com/product/282/neutron?lView=rd&lTagFamily=%23issue&lTagSearch=download&lTagId=a11:69647b14:930661&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=100&lCategory=8590013633&lReport=50016754457

Device: Samsung J7(SM-J700F) / MMB29K
Chrome Version: 55.0.2883.91

Steps:
1.Launch chrome
2.Open http://filehippo.com/download_windows_xp_service_pack_3/download/7a20e1b8f6ef1f68b75d571eae5f581f/
3.Tap on Download

Obserevd Behavior: Download starts and Struck at 6% showing "0 Secs left".

Note: works fine on M54 54.0.2840.85 Stable

Please find the Screenshots & Logs @ go/chrome-androidlogs1/6/676453

stuck at 6% is different from stuck at 100%, although the 0 secs left seems like a wierd issue.

i was able to download the file without any issue using a Samsung J7(SM-J700H).

Network condition is likely to blame if a download stuck at less than 100%, but stuck at 100% is very strange

Yeah especially if it's just happening this release to a bunch of people.  I'm trying to go through the logs to see if there's anything obvious with the notifications we're attempting to show.

There are two separate problems in this bug. THe first is that the downloads is stuck at 100% - this appears to be related to the unsafe download infobar not being accepted. This will be rectified in M56 where we tie the infobar and notification are connected.

The second issue is the download is stuck at 6% (0 secs left). This appears to be a wifi issue. We need to figure out how we can better handle this situation in the future.