On Aug 27, 9:30 pm, Perlover <[EMAIL PROTECTED]> wrote:
> Hello!
>
> For repeating the bug i do:
>
> 1) I have a big AJAX document, there many nodes of DOM (big table),
> nodes are made by script in document. I cannot present this document
> here

Of course this means we cannot be of much help.

> 2) I have Firebug 1.2.0 (i don't know the beta number, but i see 1.2.0
> version in my Addon's list) and Firefox 3.0.1
>
> I do:
>
> 1) Load my big ajax document. This document does many inserts in DOM.
> Now there no problem - 100% CPU loading only during 6-9 seconds and
> CPU idle after ... I work
> 2) I click Firebug icon in taskbar, i see now sub-window of Firebug
> and do Inspect any link in my table. All Ok here
> 3) After i click by Firebug icon again and Firebug sub-window hides. I
> think that firebug disabled. And i cannot disable one by other a ways
> anyways

If the Firebug icon in the status bar is orange, then the debug
listeners are on. As far as I know this test is 100% reliable. Orange
On, Gray Off. No other info is that reliable.

> 4) Now i do reload my Tab where my big document. There no a Firebug
> sub-window. I think that all is OK, Firebug is disabled. But here i
> see 100% CPU eating during 30-40 seconds and may be more time. I

Any chance you omitted some steps here?  Please tell us if
1) Console/Script/Net panel are enabled or disabled for the site you
are loading?
2) On the script panel, is the menu next to the file-list "All" or
some other value?
3) Is the Firebug status bar icon orange or gray?

> think, the Firebug continues a tracing of DOM and when my script
> builds a DOM of new document again the Firebug traces this document.
> As well if i do menu "Suspend Firebug" between 3 & 4 points here then
> this doesn't help - i see 100% CPU eating during 30-40 seconds too. So
> i think Firebug continues a tracing of DOM even if i did "Suspend
> Firebug"

This suggests to me that your problem has nothing to do with Firebug,
or at least on with any effect we have seen before. If you Suspend
Firebug and the status bar icon is then Gray, none of that tracing
thing you imagine is in fact going on. Gray is Off.

>
> My conclusion: If i run once a Firebug for Tab window and after i
> click Firebug icon again for hiding Firebug again then Firebug doesn't
> turn off a tracing of DOM even if i reload page. As i read in

That conclusion would be correct, but it is not what you said above.
You said that you Suspend Firebug then see CPU: if so I doubt your
problem is Firebug.

> changelog there firebug should be disabled if i don't have a opened
> sub-window of firebug

I don't know where you read this so I can't help your re-interpret
this message. I do think this is a reasonable concept, but it was not
the original model of Firebug and any changes to the Firebug model
make users unhappy as we know.

jjb
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to