Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Firefox freezes/crashes immediately after completing a download

  • 2 件の返信
  • 1 人がこの問題に困っています
  • 4 回表示
  • 最後の返信者: Sollace

more options

That's pretty much it. Using Firefox 53.0.2 (64bit) I can start a download and it will progress normally until it reaches the very end, at which point the entire browser will lock up and I have to force close it through the OS.

After that I have the file I was downloading, but if I open the browser again it will either: A) Start downloading it again (I which case I can cancel the download, but my file will be deleted!) B) Immediately freeze and crash.

Opening in safe mode does nothing, and the only way I was able to get it back to a working state (short of a reinstall) was to edit my firefox profile data and manually delete the 'downloads.json' file.

That's pretty much it. Using Firefox 53.0.2 (64bit) I can start a download and it will progress normally until it reaches the very end, at which point the entire browser will lock up and I have to force close it through the OS. After that I have the file I was downloading, but if I open the browser again it will either: A) Start downloading it again (I which case I can cancel the download, but my file will be deleted!) B) Immediately freeze and crash. Opening in safe mode does nothing, and the only way I was able to get it back to a working state (short of a reinstall) was to edit my firefox profile data and manually delete the 'downloads.json' file.

すべての返信 (2)

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

  1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
  2. Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

aboutcrashesFx29

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

Here are all my reports from this month. There have been a few other incidents since (mostly relating to deviantArt's code, and power outages) so a few of the more recent ones might be unrelated. There's no way for me to tell in when they were generated though.

bp-49066559-c9a2-4d7d-ac78-32c4d0170517 5/17/17 12:21 PM bp-55d42991-7b2b-430f-b89f-32e570170517 5/17/17 12:17 PM bp-fdeda1c9-57cb-49d6-be4b-984320170517 5/17/17 12:09 PM bp-1dab2fe7-5654-43ab-a4c1-d6ed00170517 5/17/17 12:04 PM bp-30abb311-984b-45db-be0c-dc3a00170517 5/17/17 12:01 PM bp-6094dfaf-5c9b-494c-88a2-bca1f0170517 5/17/17 12:00 PM bp-9edc9742-6307-4478-a92c-9a66f0170517 5/17/17 11:59 AM bp-a96b0fcc-4af2-4e68-a10f-268aa0170517 5/17/17 11:56 AM bp-3277215c-ca73-4f9e-8b35-877250170517 5/17/17 11:56 AM bp-9d941b01-8a6b-44bd-9a95-536f71170514 5/14/17 2:51 PM bp-ec87ff2c-023e-405d-ad46-a79d41170514 5/14/17 2:36 PM bp-cbd7e8d5-a25d-4c3c-b952-7c6861170514 5/14/17 2:34 PM bp-3fb6c7ce-c6b2-4cba-b93b-4c2bd1170514 5/14/17 2:28 PM bp-8fa47e14-9890-4f32-8ac4-627ab1170514 5/14/17 2:06 PM bp-3d045150-ffc9-49a4-9536-f2f771170514 5/14/17 1:03 PM bp-30a6ddac-362c-4859-ac2c-165310170505 5/5/17 8:23 AM

The issue seems to have resolved itself for now. Though, I still don't know what the cause was so It's entirely possible it could come back at any time.

Thanks for the article! I had a look and can determine that none of those are applicable to me (except for maybe a clean install but I don't want to have to go through that if I can avoid it)