
I cannod get Firefox to complete a large download - ~356MB.
I'd been trying to download 2 large files from Icann and kept getting premature completion with Firefox. It would be showing ##MB of 356MB downloaded for a few seconds and then out of the blues it just says completed. As you can see in the shared video, I've tried this several times.
I thought that maybe one of the Firefox addons was causing the issue so I tried Troubleshoot Mode but that resulted in the same behavior.
I then went into Firefox Profile Manager and created a new profile. But that too had the same behavior - 🤔!
So I then tried Chromium. It completed the download successfully and the file passed gunzip test.
So, why is Firefox, even with a new profile, failing to complete a download?
See this video: https://youtu.be/UCYQtxljqXs
All Replies (8)
What OS? If windows, home or pro and are you running any security software besides MS Defender? What version of Firefox? What happens with this link? https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-KDE-Live-x86_64-Current.iso
Sounds like linux. If so, try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
What Desktop? X11 or Wayland?
just noticed this is mobile. What device is being used in your video?
Sorry, forgot to mention. This is on Ubuntu 24.04 with more details below:
$ > inxi -SMCIz System: Kernel: 6.11.0-1011-lowlatency arch: x86_64 bits: 64 Desktop: GNOME v: 46.0 Distro: Ubuntu 24.04.2 LTS (Noble Numbat) Machine: Type: Laptop System: LENOVO product: 21DE000KAU v: ThinkPad X1 Extreme Gen 5 serial: <superuser required> Mobo: LENOVO model: 21DE000KAU v: SDK0T76538 WIN serial: <superuser required> UEFI: LENOVO v: N3JET42W (1.26 ) date: 09/25/2024 CPU: Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP cache: L2: 11.5 MiB Speed (MHz): avg: 815 min/max: 400/4600:4700:3500 cores: 1: 765 2: 1075 3: 643 4: 400 5: 898 6: 883 7: 1483 8: 400 9: 1012 10: 400 11: 1193 12: 400 13: 955 14: 1307 15: 991 16: 1032 17: 698 18: 514 19: 400 20: 854 Info: Memory: total: 64 GiB available: 62.51 GiB used: 21.48 GiB (34.4%) Processes: 837 Uptime: 29d 23h 17m Shell: Bash inxi: 3.3.34
As for desktop:
$ > loginctl show-session $(loginctl | awk '/seat/{print $1}') -p Type Type=x11
I've had to disable Wayland as most of the software I use on Linux has successfully ported over, though that was back when I installed 24.04.1. Maybe it's time to try it again and see if all is good there now.
ak.mozilla trɔe
jonzn4SUSE said
What OS? If windows, home or pro and are you running any security software besides MS Defender? What version of Firefox? What happens with this link? https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-KDE-Live-x86_64-Current.iso Sounds like linux. If so, try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release What Desktop? X11 or Wayland?
Interestingly, I successfully downloaded that OpenSUSE KDE Live ISO file with no issue and with all my addons enabled.
I even even tried the #product-desktop-release download from Mozilla and it too had the same issue.
So, what is it with the Icann download? Remembering that I need to jump hoops to get approval to download the entire .net and .com domains, I'd imagine they are protecting their downloads some how and Firefox is unable to keep up with whatever protection mechanism is in place.
Let me know if there's anything I can collect to help you troubleshoot the issue further.
So not a browser issue. We don't have the access to do what you're doing. Maybe someone closer to dev can chime in.
I just realized I posted this in Firefox on Android accidentally. Can a moderator maybe move it to Firefox on (Linux) Desktop.
Sounds frustrating! I’ve run into similar issues before—sometimes Firefox just glitches out on certain downloads. Switching to another browser like you did is usually a good quick fix. Hopefully they sort it out in a future update.