為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox crashes

  • 8 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 philipp

more options

I had many tabs open at once in only one window. My disk came to 0 bytes of free space and the browser closed suddenly after some time. Even before freeing up space, I could reopen it and even restore my session. After deleting the folder /var/cache and restarting the OS, Firefox just wouldn't open, it just crashes, offer the option to quit or restart but clicking restart just makes the Mozilla Crash Reporter to open again.

Crash ID: bp-cc3c0dc7-ca8c-489c-bc26-6c2410180616

Don't know if it's of any help, but trying to open it through the terminal (with or without -safe-mode) the following lines are shown: ExceptionHandler::GenerateDump cloned child 7950 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...

I had many tabs open at once in only one window. My disk came to 0 bytes of free space and the browser closed suddenly after some time. Even before freeing up space, I could reopen it and even restore my session. After deleting the folder /var/cache and restarting the OS, Firefox just wouldn't open, it just crashes, offer the option to quit or restart but clicking restart just makes the Mozilla Crash Reporter to open again. Crash ID: bp-cc3c0dc7-ca8c-489c-bc26-6c2410180616 Don't know if it's of any help, but trying to open it through the terminal (with or without -safe-mode) the following lines are shown: ExceptionHandler::GenerateDump cloned child 7950 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...

被選擇的解決方法

Pkshadow said

This has not been updated : Firefox Developer Edition 61.0, please do so. So it is also a bug issue. But if update you may get out of it. As well as 0 Disk Space. So you need room for your swap file or your going to crash again. If save some room, and update maybe the fix.

I downloaded the current version from the site (61.0b14) and I'm able to launch it again, and it even restored the session. Thank you everybody for trying to help!

從原來的回覆中察看解決方案 👍 0

所有回覆 (8)

more options

MOZ_CRASH Reason Failed to get async shutdown service: NS_ERROR_FACTORY_NOT_REGISTERED

That is the reason, am sure someone who knows more will come along and look.

more options

npessoa said

My disk came to 0 bytes of free space . . . .

Most programs need disk space to work. What was the free space before starting Firefox?


Product Firefox Release Channel aurora Version 61.0b13 Build ID 20180611134439 OS Linux OS Version 0.0.0 Linux 4.16.13-200.fc27.x86_64 #1 SMP Wed May 30 15:03:53 UTC 2018 x86_64

bp-cc3c0dc7-ca8c-489c-bc26-6c2410180616 Signature: mozilla::dom::ServiceWorkerRegistrar::GetShutdownPhase const

The crash report flagged these programs;

libglib-2.0.so.0.5400.3

libgio-2.0.so.0.5400.3

libc-2.26.so

libdl-2.26.so

libpthread-2.26.so

ld-2.26.so

This is for Sumo's Related Bugs 1403348 NEW --- Crash in mozilla::dom::ServiceWorkerRegistrar::

  GetShutdownPhase
more options

Pkshadow said

Most programs need disk space to work. What was the free space before starting Firefox?

I had around 600MB free, it must have gone down because of SO updates being downloaded.

I know it's too little space, but I have to deal with it while the new SSD doesn't arrive.

由 npessoa 於 修改

more options

This has not been updated : Firefox Developer Edition 61.0, please do so. So it is also a bug issue. But if update you may get out of it. As well as 0 Disk Space.

So you need room for your swap file or your going to crash again.

If save some room, and update maybe the fix.

more options

you could try putting the following line into your prefs.js file inside your firefox profile folder and see if you're able to launch firefox afterwards:

user_pref("dom.serviceWorkers.enabled", false);
more options

philipp said

you could try putting the following line into your prefs.js file inside your firefox profile folder and see if you're able to launch firefox afterwards:
user_pref("dom.serviceWorkers.enabled", false);

It didn't work.

more options

選擇的解決方法

Pkshadow said

This has not been updated : Firefox Developer Edition 61.0, please do so. So it is also a bug issue. But if update you may get out of it. As well as 0 Disk Space. So you need room for your swap file or your going to crash again. If save some room, and update maybe the fix.

I downloaded the current version from the site (61.0b14) and I'm able to launch it again, and it even restored the session. Thank you everybody for trying to help!

more options

then please try to create a new firefox profile: Profile Manager - Create, remove or switch Firefox profiles