Problem: Stepping through program in Firebug causes Firefox to crash.
Oddities:
  -source-code line number highlights wrong
  -weird lines in watch window.. non-existant variables with numeric
names
Workaround:
  - change source-code to get recognized properly - weird vars
disappear and no more crashing.

Long version:

I'm not sure what brought this on. I've been using Firefox 9.01 and
Firebug 1.8,1.9 for a while. hmm.. I guess there was a firefox upgrade
that might've done it...

The problems began with issues trying to enable panels. I had never
had to enable individual panels using firebug before and didn't even
realize it was an option until they suddenly were disabled and I was
told to enable them. The menus to enable them weren't obvious and when
things were working better later I realized they weren't appearing
properly.

Once I was able to get the script panel enabled the crashing began. I
couldn't step through my program very far before  it would crash
firefox.

I cleared firebug, re-installed firebug. I re-installed firefox. I
tried a separate profile etc. I slept on it...

Reading on the web firebug seems to indicate any crashing bugs are the
fault of firefox. So I began looking further into issues with the
firefox installation to no avail. Firefox was only crashing when I had
firebug running.

I found some reports on the 'net pointing me back to trying a few
things with firebug. Most specifically I noticed someone write that
firebug can get confused with regard to which lines it highlights in
green ( indicating code lines where you can set a breakpoint). This is
generally when code is loading dynamically but I wasn't doing that but
I had noticed that my code and line-number highlights weren't right. I
had also noticed some strange numbers in the firebug watch window.
Where there should be named variables and values I had about 8 lines
of variables with numeric names and values such as:
5.4326e-100   2.543e235
235235     2.1e244

I noticed that the mismatched number green highlights ( I'll call them
numHL's) tended to be on closing brackets where two blocks ended one
after the other:
1  for ( var a=0; a<b; a++){
2     if( a>c){
3       count++;
4     }
5  }
where lines 4 and 5 should not be highlighted but one would be. In
some cases 2,3,4 and 5 would not be highlighted!

In the case where 2 through 5 were not highlighted ( but 2 & 3 were
expected to be) I was able to get the highlighting to appear by moving
the opening bracket onto its own line:
1  for ( var a=0; a<b; a++)
   {
2     if( a>c)
       {
3       count++;
4     }
5  }

in cases where 5 was highlighted and shouldn't be I was able to get it
corrected by adding in a line before 5 like this:

1  for ( var a=0; a<b; a++)
   {
2     if( a>c)
       {
3       count++;
4     }
       var donothing1=0;
5  }

When I did this I noticed that the funny lines in the watch window
also disappeared!

and when I tried to step through the program it didn't crash anymore.

of course.. I'd like to get rid of all those donothing vars now... but
at least I can debug!
I may have to remove the donothings just before I obfuscate and
publish? ouch.

Tried Firebug 1.9 and a few 1.8 versions
Firefox 9.0.1 <-- I'll look into getting the newest version.. or
downgrading back one.

-- 
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
https://groups.google.com/forum/#!forum/firebug

Reply via email to