Anybody else think Google Chrome browser handles downloads poorly?

I've played around with various browsers in recent years. And sometimes I download files that run to 100s of MB; the downloads from time to time are interrupted because the connection gets dropped somewhere along the line, and with the standard browsers usually I can simply resume the download without trouble. But with Google Chrome, the situation seems to be: download interrupted? sorry, you're out of luck!

I think the largest was in the 30M range. I didn't notice anything out of the ordinary.

I've only been using Chrome for about three weeks now. I can't say I'm greatly impressed.

The main thing I don't like about it is the lack of add-ons that are of any interest to me.

But I figure give it time and maybe they will come up with more.

I use RoadRunner Broadband BTW. I haven't had any interruptions on any other browsers.

interruptions

For some other browsers I used, if the download server or my ISP drops the connection, the worst I have to do is (maybe reconnect to the internet and) hit pause/resume to continue the download: if say I'm 500mb through a 600mb download and something goes wromng, I can usually recover and complete the last 100mb of the download and have what I wanted

But with Chrome, if there's some screw-up partway through the download, nothing (that I've tried) recovers and continues the partial download: no, I have to start the whole mofo over from the beginning

:grr:

I found this link:

http://www.geek.com/articles/blurb/firefox-vs-google-chrome-download-suspend-resume-ready-20080923/

"Firefox lets you pause and resume downloads. The Google Chrome browser also has a feature with the same labels. However, they function differently in one very important way. Firefox lets you pause a download, close the browser, restart the browser (even after a reboot), and resume the download. Google Chrome only lets you resume a download during a single browser session. If you close the browser, you cannot resume the download after launching it a second time. There may be an option to change this behavior. But, this appears to be the default behavior."

I have to admit, I really like Chrome though. The element inspector feature is extraordinary. But I guess you should use Firefox for downloading large files.

and I'm not talking about user-initiated download pause/resumes: I'm talking about unintended download interruptions

So far I am not a fan of using separate memory space for loading extensions. If you use 1 or 2 ok but if you have a lot your going to crash the system eventually because the really bad memory leak that Chrome has.