Why firebug slow

Re: Firebug slow It's an interesting question. Javascript handles this just fine. But it generates a warning so FF strict wants if elem. In some of our deepest nested loop do we want to add another test and take a performance hit just to fix a warning?

Honestly we've discussed it a few times and so far it has been decide it isn't worth it. So instead we are hoping and perhaps lobbying for Firefox to take out that warning. Leave a comment on davidserduke's reply. Is it easy to check for firebug? Leave a comment on jonahfox's reply.

It should be as easy as: if window. Leave a comment on scott. David Serduke schrieb:. Reply to author. Report message as abuse. Show original message.

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message. I want to debug a script after a rather lengthy initialization process. Is there any reason for this? Are there any set of reasons like maybe long js file which cause this problem?

Now if I dont find out what exactly is making firebug make my website slow, I will have to display one of those ugly Gmail style warnings. Firebug is pretty intense on the ram. Certain applications like gmail detect that firebug is opened and warn the user that they might have a slower experience than usual. I guess the developers using your website can figure on their own that if they have firebug opened it will slow down the website, right?

If not I suppose that you have no choice but detecting if FB is opened and display an error message. Firebug is a debugger. It must inject itself into Firefox in various ways in order to provide you with information you would normally not have available to you. Use it for debugging, turn it off when you don't need it, turn off the features you don't need network, script, console Firebug is basically a nice Javascript debugger. It provides traditional debugging features, like breakpoints and the ability to watch values, but it also lets you dig in and explore DOM elements.

Ultimately, if you've got a very large site in terms of client-side code and complexity then yes, Firebug can be a burden.

First of all, disable any Firebug features console, net, etc that you aren't using. The only real way to remedy this is to -try- and see if you can work on only a portion of the Javascript you need by temporarily removing some of the other code.

Generally, this just isn't feasible, but there isn't much more you can do. If you pressed F12, it will be hidden only. Switching to that tab will cause a delay sometimes, and things can feel slow in that tab too. All of this slowness started with version 2. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile. Related 0.