Breakpoints mostly ignored

[Jonas Smithson]

I'm working in Mac Firefox 26.0 with Firebug 1.12.5, which I believe are the latest versions. When I set a breakpoint inside a function in my JS code, Firebug sometimes stops there, but more often ignores it. To be clear, it may stop at a breakpoint the first time but still ignore the very same breakpoint if I reload the page. At that point it basically ignores all breakpoints from then on, and I have to restart Firefox to get it to see them again -- just disabling/enabling Firebug doesn't help.

Sometimes it will obey the breakpoints and the step buttons, but ignore the "play" blue triangle button. The console is still working fine in all cases, but as time goes on it seems to ignore my breakpoints more and more.

Are other people experiencing this? Any suggestions? Thanks.

[Jonas Smithson]

Sorry to reply to my own post, but I may have tracked down the problem, and perhaps others can benefit from what I found.

I noticed that breakpoints were working fine, on the same code, in my Windows 7 versions of Firefox + Firebug. I have far more extensions in Mac Firefox (my primary devel environment) than in my Windows copy. On a hunch, I turned off FirePHP (an extension for Firebug, which I only had installed in the Mac version) from within its own popdown menu. Didn't help. Then I disabled FirePHP completely via my Firefox Extensions list, and relaunched Firefox. The problem seems to be solved: the breakpoints in Mac Firebug now behave normally.

So... it seems there may be a conflict between FirePHP and Firebug breakpoints. Unless, of course, it was a coincidence (since the problem was intermittent to begin with). Anybody else notice this conflict?

[Sebastian Zartner]

Did you already try that on a fresh Firefox profile with just Firebug and FirePHP installed? If you can break it down to a small test case and ensure that it's a conflict with FirePHP, you should report that in its issue tracker. I also CC'ed Christoph Dorn, the author of FirePHP.

Sebastian

[Jonas Smithson]

No, sorry, I don't have time to play around with new or alternate Firefox profiles now and do more tests. I once had some kind of utility that let me switch between different profiles, but I found it awkward and confusing and it messed up my development environment somewhat. So I'm afraid I'll just have to leave it at the description I already gave. I'll just have to remember to enable FirePHP only when I need it, which isn't that often, since I spend a lot more time in JavaScript.

--
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+u...@googlegroups.com.
To post to this group, send email to fir...@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/57faba45-c6ed-4948-9411-934a19c6a10a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Sebastian Zartner]

No, sorry, I don't have time to play around with new or alternate Firefox profiles now and do more tests.

I see.
 

I once had some kind of utility that let me switch between different profiles, but I found it awkward and confusing and it messed up my development environment somewhat.

Note that you don't need any special tool to create a new profile. You just need to call Firefox from the command line with the parameter -p. Anyway, thanks for the info.
@Christoph: Did you experience this issue yet?

Sebastian