搜索 | 用户支持

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

详细了解

Tab crashed when open a web page

  • 17 个回答
  • 2 人有此问题
  • 2 次查看
  • 最后回复者为 Yegorius

more options

I just used pacman to update to the latest Firefox, but the tab crashed each time I open a new web page ( I can open settings, about:xxx and etc... ). I tried Troubleshoot Firefox crashes and it did not crash in troubleshoot mode. Then I tried extensions, themes and hardware acceleration issues to solve common Firefox problems https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems but non of these options solved the problem. I disabled all extensions, themes and hardware acceleration, and it reported the same error.

I just used pacman to update to the latest Firefox, but the tab crashed each time I open a new web page ( I can open settings, about:xxx and etc... ). I tried [https://support.mozilla.org/en-US/kb/troubleshoot-firefox-crashes-closing-or-quitting?redirectslug=Firefox+crashes&redirectlocale=en-US Troubleshoot Firefox crashes] and it did not crash in troubleshoot mode. Then I tried [http://Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems] but non of these options solved the problem. I disabled all extensions, themes and hardware acceleration, and it reported the same error.
已附加屏幕截图

被采纳的解决方案

This bug has already been fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1664151 Temporary workaround is to set `gfx.e10s.font-list.shared` to false.

定位到答案原位置 👍 1

所有回复 (17)

more options

Correct Link for the second one

more options

2014762174a said

I tried Troubleshoot Firefox crashes and it did not crash in troubleshoot mode

It could be the work of one of your add-ons, or it could be Hardware Acceleration. How to disable Hardware Acceleration {web link}

Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control> (Mac=<Command>) <Shift> A)

In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.

Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All Of them.

If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.

Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is, detective.

more options

I already tried that and it did not work

more options

Use these links to create a new profile. Use this new profile as is. Is the problem still there?

https://support.mozilla.org/en-US/kb/how-run-firefox-when-profile-missing-inaccessible

http://kb.mozillazine.org/Profile_folder_-_Firefox#Navigating_to_the_profile_folder

https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles


Type about:profiles<enter> in the address bar.

more options

I uninstalled firefox 89.0 and compiled an esr version and solved this problem.

more options

removed

由FredMcD于修改

more options

I thought reinstall solved the problem, but it did not. I can open youtube but I cannot watch a youtube video even in the safe mode with firefox esr.

Then I used package manager to reinstalled the firefox 89.0, and it still crashed in all web pages in normal mode, but I can watch youtube in safe mode with firefox 89.0.

I have tried to remove profiles and extensions but it did not solved the problem. (I removed ~/.mozilla/)

more options

anyway I downgrade to Firefox 88.0.1-1 and it works perfectly fine right now. I'll still mark this problem Unsolved. There is no reason to stay in a non-lts version forever. If there is any new way to solve this problem please reply this post. Thanks.

more options

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

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

Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

Please, Do not post a screenshot ! !

aboutcrashesFx57

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

more options
more options

Product Firefox Release Channel release Version 78.10.1 Build ID 20210601204132 (2021-06-01) Buildhub data OS Unknown

Wed, 02 Jun 2021 17:31:56 GMT bp-1ec94659-b78f-426f-90a8-d16ad0210602 Signature: EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER

Uptime 29 seconds

Attention Sumo's there are 10 related bug reports +++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 89.0 Build ID 20210531160138 (2021-05-31) Buildhub data OS Arch Linux OS Version 0.0.0 Linux 5.12.8-arch1-1 #1 SMP PREEMPT Fri, 28 May 2021 15:10:20 +0000 x86_64

Wed, 02 Jun 2021 00:07:32 GMT bp-f247c860-d6f3-4f12-8640-236a90210602 Wed, 02 Jun 2021 00:04:19 GMT bp-e632ffbb-4b46-41a9-a304-28e6f0210602 = Uptime 0 seconds

Signature: mozilla::ipc::FatalError | mozilla::dom::PContentChild::OnMessageReceived

MOZ_CRASH Reason (Sanitized) : IPDL error: "Error deserializing 'SharedMemoryHandle[]'". abort()ing as a result.

Crash Reason SIGSEGV /SEGV_MAPERR

This is for Sumo's Related Bugs 1686205 RESOLVED DUPLICATE Crash in [@ mozilla::ipc::FatalError | mozilla::dom::PContentChild::OnMessageReceived]

1664151 NEW --- Crash in [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::dom::PContentChild::OnMessageReceived] IPDL error: "Error deserializing 'SharedMemoryHandle[]'". abort()ing as a result.

more options

I called for more help.

more options

Also happens for me on FF 89 on Linux+Wayland+SwayWM. Here is one out 100 identical crash reports: https://crash-stats.mozilla.org/report/index/f5519388-4f40-4e9f-802a-3e2cb0210607

more options

bp-f5519388-4f40-4e9f-802a-3e2cb0210607 Signature: mozilla::ipc::FatalError | mozilla::dom::PContentChild::OnMessageReceived

Uptime 0 seconds

MOZ_CRASH Reason (Sanitized) : IPDL error: "Error deserializing 'SharedMemoryHandle[]'". abort()ing as a result.

Crash Reason SIGSEGV /SEGV_MAPERR

This is for Sumo's Related Bugs 1686205 RESOLVED DUPLICATE Crash in [@ mozilla::ipc::FatalError | mozilla::dom::PContentChild::OnMessageReceived]

1664151 NEW --- Crash in [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::dom::PContentChild::OnMessageReceived] IPDL error: "Error deserializing 'SharedMemoryHandle[]'". abort()ing as a result.

more options

Yegorius said

Also happens for me on FF 89 on Linux+Wayland+SwayWM. Here is one out 100 identical crash reports: https://crash-stats.mozilla.org/report/index/f5519388-4f40-4e9f-802a-3e2cb0210607

I am using Arch+Xorg+Plasma with FF 89

more options

I am also on Arch. Previously I thought this problem was due to Wayland, but since it also happens on Xorg this is probably Linux specific.

more options

选择的解决方案

This bug has already been fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1664151 Temporary workaround is to set `gfx.e10s.font-list.shared` to false.