Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefoy Android: How to kill dead hidden downloads?

  • 1 个回答
  • 1 人有此问题
  • 11 次查看
  • 最后回复者为 TyDraniu

more options

Hi everyone!

I tried to download .pdf files from the web. Due to bad internet connection this was not possible at that time. So Firefox informed me that the download has failed, and I accepted this message and intended to start the process later with Wifi again from scratch. My FF download file list is actually empty.

Nevertheless Firefox tries every 15min to download these files, maybe due to a hidden reminder or entry, and every time I am informed that the download failed again and again and again...

How do I terminate (dead/stopped) downloads that I cannot find, finally?

Yes, forcing the app to stop and clearing all data (cache only is not sufficient) kills the dead hidden links, too, but I don't want to set up FF everytime when this occurs.

Thank you very much for your support.

Best regards - Thorsten Samsung Galaxy Note 3, Android 5.0

Hi everyone! I tried to download .pdf files from the web. Due to bad internet connection this was not possible at that time. So Firefox informed me that the download has failed, and I accepted this message and intended to start the process later with Wifi again from scratch. My FF download file list is actually empty. Nevertheless Firefox tries every 15min to download these files, maybe due to a hidden reminder or entry, and every time I am informed that the download failed again and again and again... How do I terminate (dead/stopped) downloads that I cannot find, finally? Yes, forcing the app to stop and clearing all data (cache only is not sufficient) kills the dead hidden links, too, but I don't want to set up FF everytime when this occurs. Thank you very much for your support. Best regards - Thorsten Samsung Galaxy Note 3, Android 5.0

所有回复 (1)

more options

Right, this is known issue and should be fixed in the next version.