Re: firebug performance problem w/web application

2009-08-09 Thread Ed Abrams

So far, with the tracing version, I have been able to reproduce the
problem and make my mac go crazy on the fans (CPU maxed out), but I
have not yet thrown the stop script exception that will give the line
number.  I'll keep trying.  It would be helpful to know whether other
people with the same platform can reproduce this.

-Eddie

On Aug 5, 2:08 pm, johnjbarton johnjbar...@johnjbarton.com wrote:
 Eddie, please install Firebug 1.4X.2, open the tracing window with
 ERRORS set, and repeat the test, post the trace on our bug report
 list.
 More info:http://groups.google.com/group/firebug/web/faq-about-firebug.
 I'll post back here with the results.
 (The line number in 1.4.2 are different from 1.4X)
 jjb

 On Aug 5, 10:32 am, Ed Abrams zeroaltit...@gmail.com wrote:



  Hello,

  Here is my platform: Mac OSX Leopard (10.5.7).

  Here is my browser: Firefox 3.5.2 (Build identifier: Mozilla/5.0
  (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.2) Gecko/20090729
  Firefox/3.5.2)

  Here is my Firebug: 1.4.2

  Problem: Crazy-badperformancein any window under test case

  Test case:
   * open firefox 3.5 and several tabs
   * in one tab, go to gmail.com
   * disable firebug
   * go to gmail.com
   * verify thatperformancein all cases is normal
   * enable firebug
   * enable every firebug panel EXCEPT console (disabled)
   * verify thatperformancein all cases is normal
   * enable the CONSOLE
   * in gmail, click 'compose message'
   * start typing

  PROBLEM: theperformancehas become so bad that the characters you're
  typing only appear at a rate of 1 character per second.  Every other
  tab and window is alsoperformance-hit.  If you try, you can get the
  'stop script' dialog to appear, which cites a Firebug script, lib.js,
  at line 1176 (I think -- I should double check) as being the lagging
  line.

  I hope this helps.

  -Eddie

  On Aug 4, 3:21 pm, Prefontim prefon...@hotmail.com wrote:

   I am also getting extremely slowperformancewith 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 ask...@gmail.com wrote:

@SteveG:

I am seeing pretty goodperformanceacross all tabs at this point.  I
can pretty much just leave firebug on all the time now w/out seeing
any undueperformancehit.  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/Firefoxperformanceissue.  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 sgehringdes...@gmail.com 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 ask...@gmail.com wrote:

  After a bunch of digging, I found a Firefoxperformancetweak 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 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
-~--~~~~--~~--~--~---



Re: firebug performance problem w/web application

2009-08-05 Thread Ed Abrams

Hello,

Here is my platform: Mac OSX Leopard (10.5.7).

Here is my browser: Firefox 3.5.2 (Build identifier: Mozilla/5.0
(Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.2) Gecko/20090729
Firefox/3.5.2)

Here is my Firebug: 1.4.2

Problem: Crazy-bad performance in any window under test case

Test case:
 * open firefox 3.5 and several tabs
 * in one tab, go to gmail.com
 * disable firebug
 * go to gmail.com
 * verify that performance in all cases is normal
 * enable firebug
 * enable every firebug panel EXCEPT console (disabled)
 * verify that performance in all cases is normal
 * enable the CONSOLE
 * in gmail, click 'compose message'
 * start typing

PROBLEM: the performance has become so bad that the characters you're
typing only appear at a rate of 1 character per second.  Every other
tab and window is also performance-hit.  If you try, you can get the
'stop script' dialog to appear, which cites a Firebug script, lib.js,
at line 1176 (I think -- I should double check) as being the lagging
line.

I hope this helps.

-Eddie



On Aug 4, 3:21 pm, Prefontim prefon...@hotmail.com wrote:
 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 ask...@gmail.com 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 sgehringdes...@gmail.com 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 ask...@gmail.com 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 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
-~--~~~~--~~--~--~---