Jim, Regarding the 17 case, try setting the script limiter (Firebug >Script > 'all' menu) to "static". Does that help? You can't debug evals this way, but maybe that is ok for your use?
jjb On Aug 19, 8:43 am, Jim Biancolo <j...@biancolo.com> wrote: > Hi John, > > *Finally* caught a break at work so I could give this more attention, > sorry about the delay! I set up a clean FF profile with only FB > installed, turned on ERRORS and DISPATCH tracing. I then went to the > TinyMCE example site above and didn't really get a freeze. I then > went to my site, which has 17 TinyMCE instances on the page, and it > appeared to freeze. But I waited it out, and several minutes later it > unfroze. So I'm guessing what I thought was a freeze was just a long > slowdown as FB dealt with processing all the crazy DOM stuff that > TinyMCE must do when it initializes. > > I have traces for both the "1 TinyMCE instance on the page" and "17 > TinyMCE instances on the page, if you're interested. Both show > errors, but I assume you can easily reproduce those errors yourself by > visiting the TinyMCE example page above, and my "freeze" is really > just a problem of scale, either from normal FB behavior as it deals > with all the TinyMCE DOM changes and whatnot, or from the errors > multiplied 17 times. Probably the former. > > Anyway, I'm happy to open an issue and attach the traces if you want, > let me know. > > Thanks again! > > Jim > > On Jul 30, 1:45 am, johnjbarton <johnjbar...@johnjbarton.com> wrote: > > > To be clear I see the error message, not the freeze. I kinda doubt > > these are related. > > > You can install the tracing version, > > 1.5X.0a20,http://getfirebug.com/releases/firebug/1.5X > > and set ERRORS DISPATCH. That will narrow down the place where to look > > for the freeze. > > See:http://groups.google.com/group/firebug/web/faq-about-firebug > > > jjb > > > On Jul 29, 10:35 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote: > > > > I can see this effect. Firebug thinks there are two windows with the > > > same URL. It adds the console element to both of them, but then when > > > it looks again one of the windows does not have the element. Or so it > > > seems so far. > > > > jjb > > > > On Jul 29, 2:16 pm, Jim Biancolo <j...@biancolo.com> wrote: > > > > > Hi folks, > > > > > I'm running FF 3.5.1 and Firebug 1.4.1, and am having a devil of a > > > > time using Firebug on some of my pages. With Firebug disabled, the > > > > page works fine, validates, etc. But with Firebug enabled, I get this > > > > error in the console: > > > > > "Firebug cannot find _firebugConsole element true" > > > > > ... and Firefox freezes up until I hit "Stop" on the page load (can > > > > take awhile before it accepts the "Stop" click, too). Unfortunately > > > > the pages aren't public, but I think the problem relates to TinyMCE. > > > > I get the same error if I go to the TinyMCE examples page with Firebug > > > > enabled: > > > > >http://tinymce.moxiecode.com/examples/full.php > > > > > Does anybody else get this behavior? My pages worked fine under FF > > > > 3.0.x and Firebug 1.3.x. > > > > > Thanks! > > > > > Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
