Op zondag 6 juli 2014 22:06:54 UTC+2 schreef Sebastian Zartner: > > On Sunday, July 6, 2014 5:41:24 PM UTC+2, peterbo...@gmail.com wrote: >> >> At the moment Firebug is not an option anymore for me. My main problems >> are with the debugger: >> - it's impossibly slow. Every single action takes several seconds. >> > Really? As far as I saw only switching between scripts takes a bit longer > than before. Improving the performance of this is reported in issue 7560 > <https://code.google.com/p/fbug/issues/detail?id=7560>. > If other parts are slow, too, could you please try to run Firebug on a > fresh profile > <https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile> > and tell us if it's better? > Yes, really. A fresh profile with only Firebug 2.0.1 doesn't change a thing. It takes over 10 seconds to even appear after pressing F12, and even scrolling through the JS code is extremely sluggish.
> > - flashing of other windows when stepping through the code >> > Sound like issue 7512 > <https://code.google.com/p/fbug/issues/detail?id=7512>. Is it this what > you see? > Yes, and the other window doesn't even have to be minimized > > >> - breakpoints that are being ignored even when the code is clearly >> executed >> > Some breakpoint issues are fixed in Firebug 2.0.2 > <https://addons.mozilla.org/firefox/addon/firebug/versions/2.0.2> (which > is currently on review on addons.mozilla.org). Please try it out and let > us know if it fixes your issues. If not, it would be great if you reported > the problem <https://code.google.com/p/fbug/issues/entry> and attached a > simple test case with steps to reproduce, so it can be fixed. > Hard to tell - it doesn't happen consistently > > >> - watches that insist of scrolling just out of view even though the >> content of the window didn't change >> > I guess that's the same as reported in issue 4201 > <https://code.google.com/p/fbug/issues/detail?id=4201>, right? > More or less - it does seem to scroll down, but only just short of where it should be scrolling. > > Sebastian > Oh, and try and set a breakpoint in a dragover handler - the cursor changes to nodrop, in all Firefox windows, and you can't click anything. BTW - I'm not really looking for these issues to be resolved. With every new version both FF and FB are getting slower and slower in spite of running on a hex-core 16GB machine, and I just wanted to chime in and let you know that the current state of things is just not working for me. I'll be keeping an eye on how things develop over the coming months, and maybe come back to using FB again, because I do like it and I've gotten used to it. For now I'll be developing in Chrome though. :( -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/36d6b0f1-d314-47ea-93b8-84e539c3b399%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
