On Aug 31, 4:35 pm, Evan Dorn <[EMAIL PROTECTED]> wrote:
> I have performance problems whenever firebug is installed.
> Specifically, there is about a two second period after the loading of
> every page before firefox will respond to user input (i.e. no
> scrolling, no clicking, etc.) Occasionally, similar pauses in UI
> responsiveness even while I'm on one page ... I suspect but can't
> prove that these happen when pages load or otherwise refresh in the
> background. As an example, it's happened thrice while typing this
> message; in each case, the cursor stopped blinking and the letters I
> was typing
>
> Here are the two key bits of information:
> 1) I have console, script, and net turned off entirely.
> 2) These pauses go away if I disable Firebug using the Add-Ons menu
> and restart FF.
>
> So, I'm quite sure these frequent pauses are caused by Firebug, but
> contrary to the documentation and FAQs, they are not resolved by
> disabling the three panels for which disable is available.
>
> I would love a feature to disable firebug entirely - including HTML,
> CSS, and DOM, because these *do* cause performance problems for me.
Well you have a performance problem and you have demonstrated that it
goes away when you disable from the Addon. But it does not follow
that the problem is caused by HTML/CSS/DOM. We don't know the cause.
Based on our information these functions have no over head unless you
use them. There are other potential sources of this problem.
Does it matter if Firebug's UI is open?
What happens if you use Suspend Firebug?
Do you have lots of tabs open (200?)
> Disabling it in FF Add-Ons is tedious because I have to restart the
> browser. A return to the Firebug 1.0 way of disabling it entirely,
> but enabling it only for some sites, would be really appreciated.
> (Though that never quite worked for me; often firebug would still pop
> up even when "Disable Firebug" was checked).
Firebug 1.0 never had a way of disabling it entirely. There are not a
lot of changes to HTML/CSS/DOM between 1.0 and 1.2. The only thing I
can imagine is that we are refreshing these views (which can be
expensive in some cases) when we should not. How do you propose we
determine if this may be a problem?
>
> Thanks!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
