Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

silent crash on galaxy s3

  • 2 одговорa
  • 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.