Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

CRASH....REPORT....CRASH....REPORT....CRASH....REPORT....CRASH

ztag88
ztag88
more options

Like it says.....Firefox keeps crashing (with no apparent cause), at any time, on any site, whether active or idling. ....Then it asks to be sent a report. ....and so I send yet another report.

Then, it might be 2-minutes, or 2-hours later...it crashes again.

It seems random.

And I am clearly not the only one experiencing this.

When will Mozilla FIX this raging problem?

When it becomes the top-Googled subject?

-Galaxy Note 4 with latest KitKat, and Firefox 36.x........crash, crash, crash....report, report, report.

-Galaxy Note 4 with latest KitKat, and Firefox 37.x........crash, crash, crash....report, report, report.

-Galaxy Note 4 with Lollipop update, and Firefox 37.x........crash, crash, crash....report, report, report.

-REPLACED Galaxy Note 4 with Lollipop update, and Firefox 37.x........crash, crash, crash....report, report, report.

At all times, device was in perfect health, and Firefox reported itself as being in perfect health.

Verizon Wireless Data.

High-Speed Broadband MediaCom (blecchh) cable-based internet service.

Has Mozilla been HACKED?

CRASH....REPORT....CRASH....REPORT....CRASH....REPORT....CRASH...

And Mozilla is in hiding, as we get no answers, and no solutions.

We are all supposed to gather in some forum, and weep and lament, never to hear anything from those who could ever really help.

I tried Chrome and had no such issues.

I never would have tried Chrome, if not for this unresolved, un-addressed, recurring crash-problem.

Firefox has become like a feeble candle that blows out when there is not even a breeze.

Like it says.....Firefox keeps crashing (with no apparent cause), at any time, on any site, whether active or idling. ....Then it asks to be sent a report. ....and so I send yet another report. Then, it might be 2-minutes, or 2-hours later...it crashes again. It seems random. And I am clearly not the only one experiencing this. When will Mozilla FIX this raging problem? When it becomes the top-Googled subject? -Galaxy Note 4 with latest KitKat, and Firefox 36.x........crash, crash, crash....report, report, report. -Galaxy Note 4 with latest KitKat, and Firefox 37.x........crash, crash, crash....report, report, report. -Galaxy Note 4 with Lollipop update, and Firefox 37.x........crash, crash, crash....report, report, report. -REPLACED Galaxy Note 4 with Lollipop update, and Firefox 37.x........crash, crash, crash....report, report, report. At all times, device was in perfect health, and Firefox reported itself as being in perfect health. Verizon Wireless Data. High-Speed Broadband MediaCom (blecchh) cable-based internet service. Has Mozilla been HACKED? CRASH....REPORT....CRASH....REPORT....CRASH....REPORT....CRASH... And Mozilla is in hiding, as we get no answers, and no solutions. We are all supposed to gather in some forum, and weep and lament, never to hear anything from those who could ever really help. I tried Chrome and had no such issues. I never would have tried Chrome, if not for this unresolved, un-addressed, recurring crash-problem. Firefox has become like a feeble candle that blows out when there is not even a breeze.

Wot ztag88 změnjeny

Wšě wotmołwy (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

In order to share your crash reports with forum volunteers, we need the crash report IDs. If you open a new tab and edit the URL to about:crashes and tap Go, you should see a list of links starting with bp-. Those are the numbers we want. Hopefully you can figure out a way to copy/paste them into a reply. (If you press and hold on Report, you then can extend the selection down to the bottom by dragging the selection end marker.)