Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Firefox crashes and causes other apps to crash too

  • 11 wótegrona
  • 1 ma toś ten problem
  • 18 naglědow
  • Slědne wótegrono wót user633449

more options

This is not a duplicate of 792342 because several actions make it crash. Some times it crashes at start. Fire fox has been crashing every day. Actually every hour. After the crash, everything else starts crashing too. It started about 5 days ago. I've been logging the crashes using aLogRec and aLogCat. I'll try to include the files in this report. Sadly, I still couldn't isolate the issue for reproduction. Once it crashed at start. Once it crashed using facebook (aparently some javascript bad coding or bad interpretation when clicking the message buttom in facebook's site). What I surely know that always happends is that I only can use the device again after turning it off and on again (resetting makes it crash from start or loop).

This is not a duplicate of 792342 because several actions make it crash. Some times it crashes at start. Fire fox has been crashing every day. Actually every hour. After the crash, everything else starts crashing too. It started about 5 days ago. I've been logging the crashes using aLogRec and aLogCat. I'll try to include the files in this report. Sadly, I still couldn't isolate the issue for reproduction. Once it crashed at start. Once it crashed using facebook (aparently some javascript bad coding or bad interpretation when clicking the message buttom in facebook's site). What I surely know that always happends is that I only can use the device again after turning it off and on again (resetting makes it crash from start or loop).

Wšykne wótegrona (11)

more options

We're sorry to hear that your Firefox seems to be crashing. Please perform the following steps to give us a crash report ID that helps us find out more about the cause of the crash.

  1. Enter about:crashes in the Firefox location bar (that's where you enter your website names) and press Enter. You should now see a list of submitted crash reports.
  2. Copy the most recent 5 report IDs that you see in the crash report window and paste them into your forum response.

Thanks in advance for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

These are the two first logs I recorded: http://db.tt/Jl0Avjjw http://db.tt/4RiIk1EP

more options

These are other three (recorded yesterday): 1. http://db.tt/kJp87qJU 2. http://db.tt/TRqqpu1j 3. http://db.tt/hDFIZ2XU

more options

Just for your information, this is a link of a total crash that happened after restarting the device (instead of turning it down and on again, after firefox crashed). http://db.tt/MW8o2SF2

more options

I'm gonna folow the instructions "about:crashes" right now. By the way, it's important to inform that, when it crashes, it asks to send a report. As far as I understand from the data recorded by aLogCat (I'm just a lawyer), although I authorize it to send the report, it fails to do so.

more options

Sadly, there was only one crash in the list: bp-2e5a171a-27fa-42e0-b997-f721d2121104 http://crash-stats.mozilla.com/report/index/bp-2e5a171a-27fa-42e0-b997-f721d2121104

more options

By the way: I checked the autogenerated bug report. According to the date and time of the generation, it doesn't have anything to do with my issue. Sadly, you'll have to relly on the data generated by aLogCat and aLogRec.

more options

First, please update Firefox to 17, and see if you can reproduce the crash.

more options

Also, the crashes that have a crash ID on our servers are the only ones really useful to us right now.

more options

Then forget about it. It is the latest version. It has automatic update turned on. It has always been the latest version.

more options

Well the version in the crash said said it was 16.0.2, which is about 3 months old now.