4 ms·
For about a year, Firebug was horribly unstable for me. It seemed that each time they introduced a bunch of new features, the crashing, hanging, and erratic beh
by gruseom 17y ago
For about a year, Firebug was horribly unstable for me. It seemed that each time they introduced a bunch of new features, the crashing, hanging, and erratic behavior (e.g. breaking at a line of source code far removed from the actual breakpoint) got worse. Happily, though, the last release before this current one reversed that trend. It didn't eliminate the problems but it did make them tolerable, which was a relief. I hope this one doesn't revive the previous tradition!
I think part of the problem is that FB wasn't designed to work with large (or even medium-sized) JS programs. We bundle all our JS into one HTTP request. It's a few thousand lines, which is big enough to cause FB noticeable trouble. A lot of the fancy features they've been adding are pretty useless to me; I wish they would simply make the console and the debugger rock solid. (And fix things like the horrible way they print arrays...)
- abdulhaq 17y agoWhat I do is have a separate *_debug.html page, which loads the js files individually. I.e., I have a python build script that auto builds the main.html and main_debug.html from much smaller html, css and js files. This is particularly useful when debugging older versions of IE. For the live non-debug version I also YUI-compress the concatenated js file.
- gruseom 17y agoJust to follow up on my earlier comment: so the new Firebug crapped out the very first time I tried to use it. I've already reverted to 1.4. I don't understand this project. Serious web app developers are, I guess, not their target audience. Edit: it's not like 1.4 works either. I set breakpoints and they just get ignored. Grrrrr. Edit 2: so I resort to putting "debugger" keywords in my JS and Firebug breaks into the debugger at an entirely different source location. Grrrrr ^ 2.