4 ms·
I recently tried switching back to FF from Chrome and I find FF to lag horribly. Downloads are frequently broken and stall. The <filename>, <filename.part> thin
by sitkack 13y ago
I recently tried switching back to FF from Chrome and I find FF to lag horribly. Downloads are frequently broken and stall. The <filename>, <filename.part> thing is ridiculous. It feels like there is a molasses powered queue between input events and response, FF feels like a drunken master. I am in Chrome right now, I wish I was in FF.
- rangibaby 13y agoBroken / stalled downloads don't sound like a Firefox problem to me. If you can reliably get a DL to fail in Firefox (that works fine in another browser) and reproduce it, file a bug :-)
- sitkack 13y agoI can't get things to reliably fail, admittedly the connections I am on are flaky. I have been traveling around the world for the last 8 months. From direct experience I know that Chrome handles flakey connections much better than FF. I routinely get downloads that are completely stuck in FF, showing 20KB/S as a download speed but the file hasn't been touched in 5 minutes and nothing gets written to disk and the activity monitor shows 0KB/s of network traffic. I would open a bug, but I would have to write a server that would expose the problem, no decent repro case and it wouldn't get fixed. ---- edit, Many times I have to pause a download and then resume to get the dl unstuck.
- 616c 13y agoI refuse to install Chrome, but do install the pure open-source Chromium. I routinely get that behavior with Chrom[e|ium], which leaves files with a crx extension littered throughout my Downloads directory. But to be fair from both our ends, neither is that useful individual anecdote(s) != empiricism.
- sitkack 13y agoYeah, I have been toying with how to write a server to automated test cases to repro these bugs. Almost all issues I have with browsers is how they behave on slow connections. On the very fast and reliable connections we have in the states, many of the issues are not present.
- robin_reala 13y agoThe <filename>, <filename.part> thing is ridiculous. Yep. Luckily it’s being fixed as we speak: https://bugzilla.mozilla.org/show_bug.cgi?id=420355 https://bugzilla.mozilla.org/show_bug.cgi?id=420355
- tmzt 13y agoIt's actually quiet nice to be able to rename the file and wget -c it. I don't know if .crdownload has a header, but it doesn't seem to work the same way.
- brusch 13y agoThat's strange the only browser I got problems with downloading files is Chrome. Sometimes it takes a long time between clicking the download and seeing any visual clue from chrome that it started the download.