Can you explain what you mean by "FB crashes"? Firefox can crash (exit due to incorrect machine instructions), but Firebug cannot. jjb
On Jul 14, 10:20 am, Mike Walters <[email protected]> wrote: > im trying to get a simplified test case, however... here's 1 of the things > ive noticed and mentioned above. > <html> > <head> > > </head> > <body> > <script> > var AAA = {hello:'world'}; > debugger; > eval("var abc = Failure;"); > </script> > </body> > </html> > > ... this will eval and fail, which has you in the debugger. hit continue, > and notice the stack is still viewable on the right. Im not saying this is a > problem, i wouldnt mind seeing the stack still if there really was a > failure... just seems this is always the case when FB crashes. > > ~m > > On Tue, Jul 14, 2009 at 12:40 PM, johnjbarton > <[email protected]>wrote: > > > > > If you open a bug report with a test case I can look into it. > > jjb > > > On Jul 14, 9:19 am, Mike Walters <[email protected]> wrote: > > > I can get this to occur by putting a "debugger;" statement in... and 1 of > > 2 > > > ways somehow triggers the event. 1. do not hit continue (or F8) and then > > > just refresh the webpage. 2. Continuing (or hitting F8) sometimes causes > > the > > > debugger to do a weird thing where the script tab seems to have moved on, > > > however the json windon (on the right) appears to still contain stack > > > objects. > > > After 1 of these 2 happen, the debugger is broken. Consequently if you > > have > > > afformentioned code (martinez wrote) in your script it seems firebug is > > just > > > done for. Gotta kill the tab, and open a new one... and sometimes you > > have > > > to kill THAT one and open yet another to get it to work right. Killing > > the > > > browser and restarted also will fix it. > > > > ~m > > > > On Tue, Jul 14, 2009 at 12:08 PM, johnjbarton > > > <[email protected]>wrote: > > > > > I don't know if it even a bug yet, or if there is anything we can do > > > > about it. > > > > jjb > > > > > On Jul 14, 8:37 am, Mike Walters <[email protected]> wrote: > > > > > Has this been resolved, its a pretty annoying bug? I have to kill the > > FF > > > > tab > > > > > and open a new each time this occurs.~m > > > > > > On Fri, Jul 10, 2009 at 1:33 AM, johnjbarton < > > > > [email protected]>wrote: > > > > > > > We would appreciate this info in a bug report to consider it > > further: > > > > > > >http://code.google.com/p/fbug/issues/list > > > > > > > jjb > > > > > > > On Jul 9, 8:34 am, amartinez <[email protected]> wrote: > > > > > > > Not sure if this is just a FF3.5 / Firebug 1.4x.0b7 issue, but > > the > > > > > > > following line of code can cause Firebug to stop working. I do > > not > > > > > > > know enough about extension development to make a call on whether > > > > this > > > > > > > is an issue or not, but I figured it might help some poor soul > > out. > > > > > > > > if(false){ var console = {} } > > > > > > > > Even though the if statement fails, it will cause Firebug to > > throw > > > > the > > > > > > > following errors and cause the console to stop working when you > > > > > > > actually expand Firebug and click on the console's command line. > > > > > > > > > Firebug cannot find _firebugConsole element true Window <site > > > > address> > > > > > > > > redeclaration of var console > > > > > > > > This same script will not cause any issues if the key word 'var' > > is > > > > > > > removed (e.g. if(false){console = {} } ). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
