I am also getting extremely slow performance with Firebug 1.4.x on FF 3.0. Firebug 1.3.3 did not have this issue. I disabled all other plug-ins, but that did not help. Then, I tested it on a new profile, and that did not help either. Firebug is too slow to be usable at this point. I will have to use 1.3.3 (which is also almost too buggy to be usable) for now.
On Aug 4, 10:38 am, ak732 <[email protected]> wrote: > @SteveG: > > I am seeing pretty good performance across all tabs at this point. I > can pretty much just leave firebug on all the time now w/out seeing > any undue performance hit. At least on any sites I've visited > recently. > > Note that the ipv6 fix had nothing to do with Firebug itself. It was > purely a WinVista/Firefox performance issue. I only thought it was > Firebug originally because it occurred coincidentally w/my creating a > new Firefox profile to try out the newer version of Firebug (and the > newer profiles are created w/ipv6 enabled by default, unlike the older > ones). > > On Jul 27, 2:12 am, SteveG <[email protected]> wrote: > > > I tried setting the network.dsn.disableIPv6 to true... but the DOM > > inspector was still preforming veryslow? > > Are there any other workarounds that you know of? > > > On Jul 21, 3:06 pm, ak732 <[email protected]> wrote: > > > > After a bunch of digging, I found a Firefox performance tweak that > > > fixed the problem. Hopefully this will help some others. In summary, > > > I changed network.dsn.disableIPv6 from true to false. > > > > 1. Open Firefox 3.x. > > > 2. Type “about:config” in the address bar and hit enter. > > > 3. In the Filter bar, enter “network.dns”. > > > 4. You should see a setting called “network.dsn.disableIPv6”. It’s > > > likely set to “false”. > > > 5. Double-click the setting “network.dsn.disableIPv6” which changes > > > it > > > to true. > > > 6. Close your browser. > > > 7. Reload the browser. > > > 8. Run the app and it should be considerably faster. > > > > This improved load times for our, admittedly resource-heavy, web > > > application by around a factor or 10. I suspect it might be a fix > > > that only matters on Windows Vista, maybe Win7. Anyway, it's easy > > > enough to try. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
