We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Firefox console or firebug crashes browser localy

  • 7 risposte
  • 3 hanno questo problema
  • 6 visualizzazioni
  • Ultima risposta di FredMcD

semafor
semafor
more options

Environment: OSX v10.12.1 Firefox 49.0.2 (but problem showed up in 49.0) Firebug 2.0.18 (but problem occurs also for ff build-in console)

I work localy using npm and gulp, I am not an front-end technologies expert but I think gulp runs web localy. Everything work fine until I turn on firebug (or console Cmd+alt+K) then firefox crashes (using memory is like 9Gb). It happens only for localy page (gulp) and it happens every time. It started when I updated ff to ver 49.0. My co-workers working on ff also have this problem.

Environment: OSX v10.12.1 Firefox 49.0.2 (but problem showed up in 49.0) Firebug 2.0.18 (but problem occurs also for ff build-in console) I work localy using npm and gulp, I am not an front-end technologies expert but I think gulp runs web localy. Everything work fine until I turn on firebug (or console Cmd+alt+K) then firefox crashes (using memory is like 9Gb). It happens only for localy page (gulp) and it happens every time. It started when I updated ff to ver 49.0. My co-workers working on ff also have this problem.

Soluzione scelta

It seems that firefox 50.0 fixes the issue.

Leggere questa risposta nel contesto 👍 1

Tutte le risposte (7)

FredMcD
FredMcD
more options

For now, disable Firebug. Also contact its support.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

aboutcrashesFx29
semafor
semafor Utente che ha posto la domanda
more options

On the 'about:crashes' last report has date '24.09.2016 09:10' but the issue I have e.g. today. Maybe I did not make a precise, sorry, in my case crashes doesn't mean that browser turns off, crashes takes few sec (10 -20 sec) after that browser with firebug works fine. (this happen every time when I turn on firebug).

Modificato da semafor il

FredMcD
FredMcD
more options

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options) key, and then starting Firefox. A small dialog should appear. Click Start In Safe Mode (not Refresh).

Is the problem still there?

semafor
semafor Utente che ha posto la domanda
more options

Unfortunately yes, problem still exists. Of course in this mode problem shows up after turn on Web console not firebug.

FredMcD
FredMcD
more options

I called for more help.

semafor
semafor Utente che ha posto la domanda
more options

Soluzione scelta

It seems that firefox 50.0 fixes the issue.

FredMcD
FredMcD
more options

That's good to hear. Please flag your last post as Solved Problem so others will know.