Does 1.3a5 hang or just the 20 lines thing? (you can just scroll to
workaround the 20 lines)
jjb
On Oct 9, 5:52 pm, SubZero <[EMAIL PROTECTED]> wrote:
> 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
>
> On Oct 10, 2:25 am, John J Barton <[EMAIL PROTECTED]> wrote:
>
> > X has tracing, for 1.3, use the Firebug menu "Open Firebug Tracing".
> > Set Options ERRORS, FBS_ERRORS, FINDDEBUGGER.
> > jjb
>
> > On Oct 9, 8:48 am, Jafar <[EMAIL PROTECTED]> wrote:
>
> > > 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
>
> > > On Oct 8, 10:41 am, John J Barton <[EMAIL PROTECTED]> wrote:
>
> > > > 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.
>
> > > > On Oct 8, 8:21 am, Jafar <[EMAIL PROTECTED]> wrote:
>
> > > > > 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.
>
> > > > > On Sep 20, 9:37 am, John J Barton <[EMAIL PROTECTED]> wrote:
>
> > > > > > 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
>
> > > > > > On Sep 20, 3:18 am, Francois Piat <[EMAIL PROTECTED]> wrote:
>
> > > > > > > > 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 (:-
> > > > > > > (((
--~--~---------~--~----~------------~-------~--~----~
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
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
