当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

silent crash on galaxy s3

  • 2 件の返信
  • 8 人がこの問題に困っています
  • 6 回表示
  • 最後の返信者: mitb66

more options

firefox seems to crash silently after some time of browsing. the crash reporter is not triggered . Just before the crash the firefox becomes unresponsive and than black screen for a couple of seconds and than return to the phone main menu screen.

firefox seems to crash silently after some time of browsing. the crash reporter is not triggered . Just before the crash the firefox becomes unresponsive and than black screen for a couple of seconds and than return to the phone main menu screen.

すべての返信 (2)

more options

hello mitb66, i haven't seen may such reports that would indicate that it is a general issue of firefox on galaxy s3 devices. so you might want to try totally resetting firefox on the phone and see if this makes a difference: go into the system's settings > apps > firefox and tap on "clear data" - this will also delete your bookmarks, passwords & history though. the app will just be as freshly installed...

more options

Hello philipp I've already tried all kinds of clearing including complete uninstall. I didn't see any improvement after clean up. Recently I've found a scenario that will cause the crash within 2-3 minutes 1. Open several (6-8) new tabs (the content is less important for the case). My test was with cnn.com. It seems to be important that new tabs are opened using context menu "Open link in new tab" 2. Add a new tab and open site flightradar24.com in it. This site seems to require a heavy processing. 3. Switch between opened tabs and perform a number of usual reading operations scrolling, zooming etc.

I've tried this scenario on my device several times and the result is always the same.