Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Firefox console or firebug crashes browser localy

  • 7 Mbohovái
  • 3 oguereko ko apañuãi
  • 6 Hecha
  • Mbohovái ipaháva FredMcD

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.

Ñemoĩporã poravopyre

It seems that firefox 50.0 fixes the issue.

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 1

Opaite Mbohovái (7)

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
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).

Moambuepyre semafor rupive

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?

more options

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

more options

I called for more help.

more options

Ñemoĩporã poravopyre

It seems that firefox 50.0 fixes the issue.

more options

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