Hey, I've logged one bug for script-tab performances issues, but I don't have time at the moment to log all of the other problems I have. My application is quite complex, so reducing many of these into test-cases will be very time-consuming.
I understand the FF developers are working very hard as well. This is just a list of problems I've noted over the last week when trying to debug. I'll eventually log these as bugs if they don't get addressed: Background: Iceweasel 30.0, Firebug 2.0.2.issue7560. My application uses RequireJS to load JS dynamically. All of these problems are new to FB 2.0 / FF 30: 1. Adding watch items in the watch panel of the "script" section: items should be added at the top where the input box is, not appended to the bottom of the list. (e.g., add two watch expressions. second one should be above the first, but FB 2.0 appends it to bottom) 2. Errors in the console have line number and a JS file. Clicking the error should highlight the line in the source. Currently it gets taken to the source page, but the line isn't marked. (Correction: sometimes it is. Sometimes it isn't. Sometimes it blinks and disappears.) 3. Sometimes breakpoints in source code are triggered during the loading of the file, rather than during the line's execution. The execution stops at the bottom of the file, despite where the breakpoint is. The file appears in the scripts list, and sometimes it doesn't. This is apparently random, and hugely annoying. Using requirejs if that makes a difference. 4. Sometimes when there's an error parsing javascript files, the console shows the file and the line number, but the script tab doesn't load the source, so it takes you to the main html page source instead. Ideally it will show you the file and the line. It feels like it's related to #3. 5. Console messages are oddly slow. When the last line of the console is an error, sometimes it takes minutes to appear (whilst apparently doing nothing...). The print buffer of the console seems to get "lazy". This is hugely annoying when there's an error on the last line because you have to wait a long time to see where the error actual is. This might be related to the FB feature where the DOM view lags behind the animation (d3.js); that is, for a 200ms visual animation, firebug might renders the DOM changes for around half a minute. This has been around for a while, but I only noticed the laggy console after FB 2.0. 6. Sometimes breakpoints stop in the wrong line. In the script view, I see the breakpoint on line 216, but it's stopping on 211 for it. (both line numbers are green (active) ) 7. Memory leaks. I have to restart FF / FB periodically because my memory keeps creeping up. I'll investigate whether this is my fault or not, but I never noticed this problem until FB 2.0 / FF 30 8. In the scripts tab, sometimes the source file is clipped. E.g., my file is 200 lines, but only say, 43 lines are shown. Sometimes it appears later, sometimes not. Hopefully this is of some use to the developers. Cheers, Glenn -- 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 [email protected]. To post to this group, send email to [email protected]. 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/84023069-c9e8-4b1d-a1a0-81848c7aadea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
