Firebug search and breakpoints do not work properly after update to FF 30 (FB 2.01)

[Marcin Karpinski]

Recently it has become impossible for me to use firebug at all.
I have been forced to use default FF debugger (which is way worse) and I am even considering switching to Chrome.

The problems started after FF got updated to version 30. Firebug did so shortly after and now I am running version 2.01.

The problem is most annoying with search and breakpoints.
When trying to do search it does not work. I am exactly sure that the phrase I am looking for is there in javascript code but when typing it and hitting next nothing happens (even with search all files checked). It sometimes gives me the correct corce code line but mostly it does not ( I cannot see any pattern in this behaviour).


Moreover when I put a breakpoint somewhere in javascript code and it reaches there, the execution stops, breakpoint is highlighted for a moment but the highlight disappears and no code navigation works. I cannot step any further or resume execution. Buttons are disabled and shortcuts (F8- >F11) do not work.

Did anyoen experience similar problems?

Regards,
M

[Bojan Jaksic]

I have the same FF and FB version as the author of the post. I am setting the breakpoints but the execution never stops at the breakpoint. I have to use

debugger;

to force stopping at the breakpoint. Is there a solution for this?

[fetis]

I have the same issues.

Moreover I have next issue with breakpoints: It stops for a moment, highlight code string and contines code execution in a second. So I cant' debug at all.

The worst update ever

[Sergey Fetiskin]

I have one more issue with breakpoints in new Firebug.

This's ghost breakpoints: I set a breakpoint, next clear it but FB
still stops on this line.


--
Best regards,
Sergey mailto:fet...@gmail.com

[Jan Honza Odvarko]

On Wednesday, June 25, 2014 11:49:24 PM UTC+2, fetis wrote:

I have the same issues.

Moreover I have next issue with breakpoints: It stops for a moment, highlight code string and contines code execution in a second. So I cant' debug at all.

This could be related to issue:
https://code.google.com/p/fbug/issues/detail?id=7567

We need a reproducible test case to fix it.

Honza

[Jan Honza Odvarko]

On Tuesday, July 1, 2014 2:37:09 PM UTC+2, fetis wrote:

I have one more issue with breakpoints in new Firebug.

This's ghost breakpoints: I set a breakpoint, next clear it but FB
still stops on this line.

This has been reported already but nobody provided a reproducible test case
(a page we can load and see the problem on our machines)

Do you have one?

If yes, please attach it to this report and we'll fix it.
https://code.google.com/p/fbug/issues/detail?id=7561

Honza

[Sergey Fetiskin]

Hello Jan,

Maybe the common point is dynamic js loading?
I'm using RequireJS to load scripts

[Jan Honza Odvarko]

On Tuesday, July 1, 2014 3:33:29 PM UTC+2, fetis wrote:

Hello Jan,

Maybe the common point is dynamic js loading?

Yep, this is most likely related to the issue.

 

I'm using RequireJS to load scripts

Any chance to access your page?

Honza

[Sergey Fetiskin]

Hello Jan,

>
> I'm using RequireJS to load scripts
> Any chance to access your page?

It's problematic. We have only minified code on production.
Maybe I can perform some tests on my side?

[Ralph Brown]

I'm seeing breakpoints that won't stop on a very simple example. This is Firebug 2.0.1 Firefox 30.0 on a Window 7 64 bit computer.

If I try to set a breakpoint on the first line of B.js in the Script tab I get a rotating wheel until I refresh the page. Only then does the red dot appear.

After that if I refresh the page, the breakpoint is hit and I can continue from it.

In the breakpoints tab, I hit the red X to delete the breakpoint. It is deleted in the breakpoints tab but the red dot is still in the Script tab 

At this point if I refresh the page the red dot in the Script tab disappears, there still are no breakpoints shown in the Breakpoints tab, but the code breaks on the first line where the deleted breakpoint was.

HTML File:

<!DOCTYPE html>

<html lang="en">

<head>

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

<meta charset="utf-8">

<title>Basic Page</title>

</head>

<body>

<h1 id="Head">AB Head</h1>

<script src="B.js">

</body>

</html>

Javascript B.js file:

var outText = "This is B";

console.log(outText); 

[Ralph Brown]

I think this may be at least partially a problem with Firefox since I'm having other weird problems with breakpoints in the Firefox debugger. In that case breakpoints aren't hit and the debugger itself seems to get into a broken state where once a breakpoint is not hit, if you close the debugger you can't reopen it. I've not seen that particular problem with Firebug, but with several bugs in the same area, I suspect something deeper in Firefox may be broken.

At least for me and my students, debugging JavaScript in Firefox is not very usable currently.

On Wednesday, July 2, 2014 1:20:15 PM UTC-4, Ralph Brown wrote:

<snip>

[Jan Honza Odvarko]

On Wednesday, July 2, 2014 7:20:15 PM UTC+2, Ralph Brown wrote:

I'm seeing breakpoints that won't stop on a very simple example. This is Firebug 2.0.1 Firefox 30.0 on a Window 7 64 bit computer.

If I try to set a breakpoint on the first line of B.js in the Script tab I get a rotating wheel until I refresh the page. Only then does the red dot appear.

I can't reproduce this behavior

I put your example online and here is what I am doing
(note that I appended closing </script> tag into your example)

1) Load http://janodvarko.cz/firebug/jsd2/tests/bp/breakpoints.html
2) Open  Firebug (F12), select the Script panel
3) Create a breakpoint at line 1 in B.js file
4) Refresh the page, the breakpoint must hit -> OK for me

Does it work for you?
If not what are your steps?

Honza

[Agustín Labaronnie]

Hello. I have exactly the same problem. I'm running Firefox 30 on Ubuntu. Tried the native debugger and Firebug 2.0.1 too, but both behave just like Marcin describes: execution stops at breakpoint, but nothing can be done, no F8, F10 nor F11 work.
Moreover, the HTML search doesn't work at all on native Firefox developer tools, but I suppose that's for another thread.

Looking forward for the solution to this issu, as I'm currently debugging with Chrome.

Regards!

[Sascha Rissel]

I am experiencing exactly the same problem: Execution stops for a second, then continues.
It's got nothing to do with dynamic sript loading, my scripts are loaded via ordinary SCRIPT-tags.

I am working on a large single page web app using ExtJS.
The bug seems to occur during the initial pass, upon the pages first rendering.

Breakpoint set within event handlers seem to work.

Please fix it, I don't like debugging in Chrome. :-/

[Sebastian Zartner]

Sascha, your problem sounds like issue 7567.
We still need a test case for it to be able to reproduce it. So it would be great if you could provide one.

Sebastian

[Matej Iličić]

In some constellations, after removal of breakpoints, debugger stops where the breakpoints were removed from (like that they were hidden, but not removed) and you could just Continue.
Continue does not work with F8 key as it used to before. F10 is working properly.

[Daniel Manta]

I had the same problem on a particular web page with iframes. The code works but I can't set breakpoints on Firebug. However the same page can be debugged normally using a different computer with same version of Firebug (or by adding "debugger;" to the code even in the computer that has the problem). None solution listed here or in Stackoverflow worked. Disabling all other extensions doesn't make any difference, creating new profile from scratch, neither. Any ideas apart from reinstalling FireFox?

[Sebastian Zartner]

If you can break this bug down to a simple test case, I suggest you create a bug report for it.

Sebastian