Hi guys, thanks for responding. Let me give you more details. > Generally if you say "crash", people will assume you mean that the > firefox process exited incorrectly. All crashes must be solved by > Firefox, Firebug can't crash Firefox even if it tries.
No, it does not "crash", it freezes the tab in which I was doing debugging. > This problem is rare but can happen. 1.4 has some effort to avoid even > these rare cases. > That post is a year and a half ago on vista and Firebug 1.0 and > Firefox 2. The thing is, I've always had this problem in FF3 - since its first day of release. If I forget to click GO button (or press F8) before reloading the page - page is blank, hourglass cursor, nothing's happening. Firebug panel is all gray, some menu items are visible, debugging icons as well - but clicking them produces no result. > > 2. Initiate debugging; > > You mean you hit the blue 'go' arrow and the page is fine right? No, I set a breakpoint on any Javascript line, run the page and execution is stopped cuz of that breakpoint. I am in a debug mode, this is what I mean by "initiate debugging". > > 3. Reload browser. > > You mean reload the page? Yes, I reload the page which I've just started debugging. > If the other tabs work fine you can just kill the tab. You don't need > to restart Firefox. Yes, but this is hardly a consolation. In fact, it's much better to terminate FF process because then I can restore the session and open the page that froze. > If you install 1.3X you can use Firebug Icon -> Open Tracing -> > Options -> Set ERRORS and BP. The trace panel Log should show you if > the debugger stopped on a breakpoint. I did that, but since I am not a Firebug expert I cannot really interpret the messages. If you have time to figure this out, I'd be more than happy to follow your instructions and send you back the result. I would love to switch to FF3 and new Firebug for development. And, there's one more thing I wanted to mention - a behaviour that's quite annoying that did not exist in Firebug 1.05. When I switch to Script tab - there's a dropdown that offers a selection of included Javascript files to debug and there's also first list item that allows to view HTML page source itself (gets selected by default on load), in case you have inline Javascript. So: 1. Choose to display any of included JS script; 2. Reload page; 3. And voila - in Firebug 1.2,1.3 the HTML file is selected again, and in Firebug 1.05 - it remembers the script I just chose and loads it. What's more, in FF3/FB1.3: 1. Place a breakpoint inside included JS file; 2. Run to that line; 3. Press F8 - and it will switch to default HTML file, closing the Javascript include that you were debugging! So, my head is spinning :-) I feel like I'm in one of those Freddie Kruger movies when only I see nightmares while everyone else thinks I'm crazy :-) Thanks, Temuri --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
