Breakpoints, "Break on all Errors" freezing UI on Mac & Linux? ff3/fbug1.2

[Jafar]

Hey, all --

I'm wondering if anyone else is seeing this behavior. If I set a
breakpoint in my code or set "Break on all Errors", especially on Mac
OS, with Firefox 3 + Firebug 1.2, when it stops at the breakpoint, the
mouse cursor turns into a watch and the whole UI of Firefox becomes
frozen. I have to force quit the browser.

In Linux, I'm seeing a similar behavior, but it's not quite the same.
I can still click around in the browser, but the debugging UI is
frozen.

Using Firefox 2 works perfectly. I haven't tested this on Windows.

I seem to recall that this was an issue for me in most betas of
Firebug 1.2, but I thought it was fixed in later ones. Now,
inexplicably, it's back.

Is anyone else seeing this?

[Kris]

I'm also seeing this on my machine (Mac, Firefox 3, Firebug 1.2.1).

[John J Barton]

Sorry I don't have a Mac. A test case with a specific file or URL and
procedure posted to the bug list would help.
http://code.google.com/p/fbug/issues/list

[mscot...@comcast.net]

I am seeing something similar. I have the previous version (1.2.0?)
and everything was working fine. I upgraded to Firebug 1.2.1, and now
stepping through code after a breakpoint is very slow. Sometimes so
slow that after a few seconds, a dialog pops up and tells me the
script is not responding, and gives me the option to continue or
cancel debugging.

What happened to the debugger?

[John J Barton]

My first guess is that this is not a change in firebug but something
else. Very little changed from 1.2.0 to 1.2.1 with regard to js
debugging.

You could try 1.3a2 in a new firefox profile. I would be very
interested in the result.

http://getfirebug.com/releases/1.3X

John

On Sep 18, 10:29 am, "mscottsm...@comcast.net"

[Francois Piat]

Hello,
I have encoutered a problem with breakpoint too, but not really the
same as the one discussed here.
When I put breakpoints and remove them they are still active in every
popup opened (FF2 & 3, FB 1.2.1)

I must say that I not very happy with this new release of FireBug
(console.log error, slower treatments, ...)

[John J Barton]

On Sep 18, 11:52 pm, Francois Piat <piat.franc...@orange.fr> wrote:
> Hello,
> I have encoutered a problem with breakpoint too, but not really the
> same as the one discussed here.
> When I put breakpoints and remove them they are still active in every
> popup opened (FF2 & 3, FB 1.2.1)

There are no bug reports on breakpoints. I'd fix them if you produce
a test case where I can see the problem.

>
> I must say that I not very happy with this new release of FireBug
> (console.log error, slower treatments, ...)

If you use FF2, issue window.loadFirebugConsole() before
console.log(). We had no choice: the console had to be reimplemented.

What is a "treatment"?

[Jafar]

John --

I'll work on producing a test case as soon as I can, and attach it to
a bug report. It also occurs to me that this problem could be due to
a change in ff 3.0.1, too. I wish I could remember exactly when
breakpoints were working for me.

I am experiencing the problem while debugging a project with huge
amounts (above 1MB, uncompressed, unminified) of JavaScript, so that
may trigger the problem, too.

Thanks also for all your hard work on Firebug -- as soon as we get
this one figured out, Fbug can once again be my main debugging tool!

- G

[John J Barton]

I recommend trying 1.3X.0a2, http://getfirebug.com/releases/1.3X. It
has better performance for large JS.

[Francois Piat]

> If you use FF2, issue window.loadFirebugConsole() before
> console.log(). We had no choice: the console had to be reimplemented.

I have try this trick, but it don't work for me ...

[Francois Piat]

>
> There are no bug reports on breakpoints. I'd fix them if you produce
> a test case where I can see the problem.

Sorry, I cannot produce a test case. I had too many problems (little,
but the sum is consequent) and I have downgrade to previous version (:-
(((

[John J Barton]

Since so many people have had success, you must have something set
into your environment which is odd. One approach that I have found
helpful is to load Firebug in to a new Firefox profile:
http://kb.mozillazine.org/Profile_Manager

Also are you running in en-US Firefox or a localized version? We have
been struggling to improve our internationalization, but its not as
solid as en-US as yet.

jjb

[Francois Piat]

Thank's for your answer. I'm working on a french XP Pro windows, but
with an en-US Firefox.
The window.loadFirebugConsole() stop the error "console not defined",
but nothing is displayed on the console.
As soon as possible, I will try a new Firefox profile as you advise
it ...

[Jafar]

Kris, I'm still working on tracking this down. What libraries and
such are you using in the project that you debug with Firebug, if you
don't mind my asking?

[Jafar]

John, all my attempts at producing a test case have failed, but I did
find a workaround that may provide a clue, or maybe point this issue
in a different direction.

In our app, firebug (and venkman!) with both freeze the UI in ff3 if
the breakpoint or error occurs somewhere within our window's load
event handler (we're actually using Prototype's Event.observe for
this, but that doesn't seem to matter). Here's the strange part: if I
wrap the contents of that event hander in a setTimeout( function()
{...}, 1 ), debugging works just fine.

[John J Barton]

Ok then my guess is that you are hitting the breakpoint and FF engine
is passing control to Firebug (firebug-service). There control flow is
routed to a deadend because of a bug. The engine is waiting for you to
debug or resume, but you have no UI to do so.

When you run under setTimeout, the stack has a different origin and
the routing algorithm takes a different path.

Some suggestions:
Try 1.3a4, getfirebug.com/releases. It has a different routing
algorithm.
Try 1.2X running Firefox.exe from the command line and FBTrace panel
FBS_FINDDEBUGGER set true (traces the routing)
Try 1.3Xa4 for double your fun.

John.

[Jafar]

No love from 1.3Xa4. Will try 1.2X in a new profile shortly...

What's the difference between 1.3Xa4 and 1.3a4?

- G

[John J Barton]

X has tracing, for 1.3, use the Firebug menu "Open Firebug Tracing".
Set Options ERRORS, FBS_ERRORS, FINDDEBUGGER.
jjb

[SubZero]

I've got this exact problem as well, running Firefox 3, with Firebug
1.2. This problem tends to occur when a breakpoint is activated when
the currently visible script in the debugger is different to the code
the breakpoint exists within. It hangs the system so badly that the
computer requires a reboot.

One scenario that this occurs in, is from within a page which issues a
XMLHttpRequest, and a breakpoint is set within the onreadystatechange
function for that object. This will hang the machine when the event
occurs. One other thing to note is that the page contains an embedded
Flash movie.

I've tried the Alpha version (1.3), and this has a bug where it
doesn't display all the source code in the page - just the first 20
lines or so.

OS: Windows XP/SP2

[John J Barton]

Does 1.3a5 hang or just the 20 lines thing? (you can just scroll to
workaround the 20 lines)

jjb

[SubZero]

Both still seem to hang. I can't scroll around the 20 lines, although
if I repeatedly scrolled down to the next page, minimise, maximise,
until I find the code, I can get around it.

The problem seems to be based around receiving certain events - in
this case a reply to XMLHttpRequest. I've actually seen the
breakpoint trigger (the breakpoint arrow shows), and then hang, with
the filesystem getting absolutely hammered, making the system fairly
unstable.

Breakpoints also sometimes don't trigger for some reason. I had to do
a refresh several times just now in order to get the breakpoint to
hit.

If there are no events triggering, Firebug works beautifully, and
breakpoints work well - it only seems to start playing up when events
are received.


On Oct 10, 11:07 am, John J Barton <johnjbar...@johnjbarton.com>

[SubZero]

As a test, setting a breakpoint on the "if (xhr...)" line will cause
Firebug to completely hang, and Firefox will have to be killed.

<html>
<head>
<script type="text/javascript">
function DisplayCategory ()
{
var xhr = new XMLHttpRequest ();
xhr.onreadystatechange = function (event)
{
if (xhr.readyState == 4)
{
if (xhr.status == 200)
{
}
}
}
xhr.open ("GET", "http://localhost:8180/code/search_xml.jsp?
category_id=154", true);
xhr.send (null);
}

DisplayCategory ();
</script>
</head>

<body>
</body>
</html>

[John J Barton]

Ok, but of course without "code/search_xml.jsp" the example only gives
an error for me.

[SubZero]

Hey, John, thanks for your replies. :) I've figured out what the
problem is, and it was the fact that it had absolutely nothing to do
with Firebug, or Firefox in general. The JSP was returning (because
of a silly code typo somewhere else in the code), a string which was
around about 30 meg in size. Hence, Javascript was choking trying to
convert this to XML. With that fixed, Firebug is working perfectly
again (not that it was Firebugs problem in the first place).

Very happy now! :)


On Oct 10, 12:48 pm, John J Barton <johnjbar...@johnjbarton.com>