搜索 | 用户支持

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

详细了解

Firefox 56 Crash ID: 1ac149f8-3fc1-4b15-839f-4da870171005

  • 3 个回答
  • 1 人有此问题
  • 5 次查看
  • 最后回复者为 Miro.Collas

more options

ID: 1ac149f8-3fc1-4b15-839f-4da870171005 Signature: EMPTY: no crashing thread identified; ERROR_NO_THREAD_LIST

FF 56 is consistently crashing when trying to access a specific web page: the "But Now" page on the Second Life Marketplace website.

FF 55 did not have this problem. I can reliably reproduce the crash when in safe mode.

ID: 1ac149f8-3fc1-4b15-839f-4da870171005 Signature: EMPTY: no crashing thread identified; ERROR_NO_THREAD_LIST FF 56 is consistently crashing when trying to access a specific web page: the "But Now" page on the Second Life Marketplace website. FF 55 did not have this problem. I can reliably reproduce the crash when in safe mode.

所有回复 (3)

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

bp-1ac149f8-3fc1-4b15-839f-4da870171005 10/5/17 4:32 PM bp-776ee261-c136-4f11-bf8f-5039b2161228 12/28/16 1:55 PM bp-7dea27a9-1682-4eab-b07c-c41012161208 12/8/16 1:57 PM bp-3aae5673-14dc-4a2e-bb95-f6ceb2161207 12/7/16 2:04 PM bp-1cf9274b-52c8-4276-b9a8-988b92161207 12/7/16 12:17 AM bp-6af0ddfb-53aa-4433-b8c2-2e58a2161127 11/26/16 10:28 PM bp-f657cc29-d927-4dbc-8bcb-dc7072161016 10/16/16 12:11 AM

more options

More info. I was able to access the web page that crashes FF, using Konqueror. Konqueror threw multiple "bad certificate" errors, but didn't crash. So maybe FF is crashing instead of handling the cert error?