Issue metadata
Sign in to add a comment
|
Download seems finished but is in fact incomplete
Reported by
moritz.h...@gmx.de,
Feb 28 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version : 48.0.2564.116 URLs (if applicable) : chrome://downloads/ What steps will reproduce the problem? 1. Download large File 2. Network error? Not sure exactly what happened... What is the expected result? Download should show up as "Failed", "Incomplete" or "Error" What happens instead? Download speed drops to 0 bytes/s. Then after a while, the download is stopped and shows up as if it finished successfully (the filename turns blue and you can click on it), but the file is incomplete.
,
Feb 29 2016
Hi, Sorry, totally forgot about the OS... I am using Windows 10 Home 64bit with the Chrome 32bit version. The Problem first occured when downloading a 400 MB ISO from Android x86 (that one only loaded halfway, but when I tried it again later, it worked) Then yesterday I was downloading the Kubuntu 15.10 amd64 image which loaded 20 MB of the 1.3 GB. I tried again and it downloaded 1.3 GB - I wasn't convinced though, so I checked the SHA 256 hash with the one provided on the website and they didn't match. I then downloaded the file with edge and it was about 3MB bigger (and the Hash matched the one online) In all three cases, the file in the download list showed up as if it finished successfuly... I can only assume it was a network fault, though I didn't experience any problems watching videos and surfing websites while the download was going. Smaller files seem to be fine also.
,
Mar 1 2016
,
Mar 1 2016
Can you capture a net-internals log showing the problem? That should allow us to see what the underlying issue is. https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Mar 1 2016
Are you behind a proxy? Also, it would be useful to have a net-internals log as mentioned in comment #4, but I'm a bit worried about the size of the log given the size of the download. The things I'm trying to determine are: * was there enough information in the headers to distinguish a early connection closure from a successful download completion. * was the server capable of byte range requests along with supplying strong validators for the entity in question, which means that Chrome can at least try to verify that the download is actually done when a connection is closed. Assuming that Chrome saw a connection close, then this would be addressed in issue 453357 .
,
Mar 2 2016
Hi, as far as I can tell, the issue described in #453357 seems to be what I am experiencing... Thanks for the feedback
,
Mar 2 2016
Thanks. I'll mark this as a duplicate of that issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ssamanoori@chromium.org
, Feb 29 2016