Re: SVG in Firebug, large memory leak?

On 12/18/09 11:04 AM, Steven Roussey wrote:
> It does not rebuild the entire HTML view AFAIK. It invalidates a node
> (and its children), and since we are at the leaf level, I don't think
> it is much. Notice how I said I think. I haven't had a need to look
> into it very deeply thus far.

Please do?  From what I've seen, the domplate setup is a huge 
performance cost when using Firebug.

> I guess I can add some temp UI to turn the observers on and off and
> test that theory, mabye as an extension to firebug. Can't just comment
> them out of the code though.

Why not, as a test?  I'd do it if I knew where the code lives; you're a 
lot more familiar with it than I am.

> I'm guessing that domplate was written a looong time ago. I don't know
> how careful the author was in handling dom references, for example. In
> domplate or everywhere.

Yes on all points.  Which doesn't help our users one bit.

To be clear, as far as I can tell from my limited testing Firebug leaks 
every single DOM object it ever touches, for the lifetime of the app. 
At least in some cases.  Fixing this should probably be a #1 priority 
for Firebug...  It's on my list of things to look into, but if someone 
with more familiarity with the Firebug code is willing to help out, that 
would help a lot.

-Boris