Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

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

了解更多

Frequent crashes on Android Firefox 23 (also 22)

  • 3 回覆
  • 15 有這個問題
  • 216 次檢視
  • 最近回覆由 kobe
  • 封存

When I first installed Firefox on my Samsung Galaxy Tab 3 7.0 it crashed continuously. Switching the "Plugins" setting from "Tap to Play" to "Disabled" reduced the crashes substantially, but they are still fairly frequent. Is there anything I can do about this? The last three crash report IDs are:

bp-e96bc9df-2c85-48a8-8b59-f19182130809 (crashed while trying to get to about:crashes) bp-6412dcd1-6880-4156-8641-6a8212130809 (crashed while trying to perform search from address bar) bp-fa2639a7-fab3-4bb3-826d-4b3872130809 (crashed while rotating view on page)

Thanks.

When I first installed Firefox on my Samsung Galaxy Tab 3 7.0 it crashed continuously. Switching the "Plugins" setting from "Tap to Play" to "Disabled" reduced the crashes substantially, but they are still fairly frequent. Is there anything I can do about this? The last three crash report IDs are: bp-e96bc9df-2c85-48a8-8b59-f19182130809 (crashed while trying to get to about:crashes) bp-6412dcd1-6880-4156-8641-6a8212130809 (crashed while trying to perform search from address bar) bp-fa2639a7-fab3-4bb3-826d-4b3872130809 (crashed while rotating view on page) Thanks.

所有回覆 (3)

This is the no5 crasher in firefox.

Have you tried firefox nightly (espically if you have updated to android 4.3).

I haven't tried nightlies, but the problem persisted in the upgrade from Firefox 22 to Firefox 23. I'm using Android 4.1.2.

I'm not sure I understand the referenced bug. Are you saying that is the cause of the three crash reports I submitted, or just suggesting I look at it? I wouldn't have thought layers would be the cause of crashes on attempting to get to pages like "about:crashes" or basic mobile searches.

Thanks.

Nope reason i posted that bug is because it is currently being worked on, and that was the crash id of yours related to it. Try the nightly.