firebug 2.0.8 stops at no breakpoints in firefox 35.0.1 on Mac or PC

184 views
Skip to first unread message

Kwooda

unread,
Feb 13, 2015, 4:41:50 AM2/13/15
to fir...@googlegroups.com
I cannot get firebug 2.0.8 to stop at ANY breakpoints in ANY of my scripts, on firefox 35.0.1 on either the Mac or the PC. If I add "debugger;" to my code, it will stop there, but when I try to set breakpoints, I just get a little animated spinner icon. When I reload the page, a breakpoint then shows up, but the code never breaks there.

What am I missing?

Manikanta A C

unread,
Feb 13, 2015, 8:42:07 AM2/13/15
to fir...@googlegroups.com
I have the problem here, I am using FF 33.1.1 on Windows.

Lawrence San

unread,
Feb 15, 2015, 1:59:24 AM2/15/15
to fir...@googlegroups.com
On my Mac, Firebug 2.0.8 seems to stop at breakpoints OK, but I'm still back on Mac Firefox 34. There does seem to be a problem with only some of the expression hover tooltips working, but mostly it seems OK.

In my Windows 7 VM, with Firefox 35.0.1, Firebug 2.0.7 (in a separate window) stops at the first breakpoint and then essentially freezes -- won't step into, step over, or play to end, no matter what I do. However, when Firebug is docked to the bottom of the main window, it behaves normally. Very strange.

After updating Windows Firebug to 2.0.8, it freezes at the first breakpoint no matter what I do, regardless of whether FB is in a separate window or docked to the bottom of the main window.

Looks like I was right not to update Mac Firefox to version 35. Now I'm going to tell VMware to roll my Win7 VM back to the last saved snapshot, so I can (hopefully) get Firebug 2.0.7 back, which is only partially broken.

If a few different people here are having similar problems, I have to wonder whether Firebug breakpoints are even being tested before new versions are rolled out.



--
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/652fa9fe-509f-4c00-b04c-5342370f1b1d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Lawrence San
Business Writing: Santhology.com
Cartoon Stories for Thoughtful People: Sanstudio.com


jasonmic...@gmail.com

unread,
Feb 19, 2015, 2:24:07 PM2/19/15
to fir...@googlegroups.com
I'm experiencing the same issue. Wasn't it supposed to be more stable after integrating with the native FireFox debugger? It seems that since the transition to FB version 2 things have become a lot more unstable. It's a pain in the butt when you can't rely on your dev tools to work at crucial moments.

Sebastian Zartner

unread,
Feb 19, 2015, 4:16:00 PM2/19/15
to fir...@googlegroups.com
That sounds related to issue 7762, 7336 and 7760. If you have a test case with steps to reproduce, please post them there.

Sebastian
Reply all
Reply to author
Forward
0 new messages