为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Firefox crashes

  • 3 个回答
  • 6 人有此问题
  • 1 次查看
  • 最后回复者为 cor-el

more options

Randomly crashes, Facebook, Banking, Google. does not matter what I'm looking at. Its crashed 3 times while trying to finish this report. Have removed all the plugins, removes Firefox and reinstalled twice today. Still unsure what is causing the crashes.

Randomly crashes, Facebook, Banking, Google. does not matter what I'm looking at. Its crashed 3 times while trying to finish this report. Have removed all the plugins, removes Firefox and reinstalled twice today. Still unsure what is causing the crashes.

所有回复 (3)

more options

There is nothing useful in the Crash ID you reported,

bp-92b6741b-beb1-4f6c-b1c3-518ec2120825
Firefox 14.0.1 Crash Report [@ EMPTY: no crashing thread identified; corrupt dump ] 

We're sorry to hear that your Firefox seems to be crashing. Please perform the following steps to give us additional crash report IDs to help us find out more about the cause of the crash.

  1. Enter about:crashes in the Firefox location bar (that's where you enter your website names) and press Enter. You should now see a list of submitted crash reports.
  2. Copy the most recent 5 report IDs that you see in the crash report window and paste them into your forum response.

Thanks in advance for your help!

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

more options

Thanks for the reply. Here are the crash ID's you asked for

bp-6a0e49c0-c966-4d4f-9f24-848572120825 8/25/2012 8:20 PMbp-92b6741b-beb1-4f6c-b1c3-518ec2120825 8/25/2012 6:12 PMbp-49731f9d-acce-4d5c-938f-004342120825 8/25/2012 6:05 PMbp-5d5c4136-0ca9-4c67-b978-9aae72120825 8/25/2012 5:57 PMbp-e7752d65-47ee-4285-b65e-121362120825 8/25/2012 1:08 PM

more options

Those are empty too: [@ EMPTY: no crashing thread identified; corrupt dump ]

Try the suggestions in this reply: