Hi,
I am working on memory leaks. IE7 has bugs that causes abnormal leaks,
but often leaks are due to wrong coding.
I would like to check how the 'window' object has changed between two
iteration of a test.
Sure, I can easily explore the window object using firebug, but our app
is massive and the window object is huge,
so I cant check it completly.
If there were a right click - 'save as' feature, then I could save the
output of the window object between two iteration,
and then run a diff tool to see what has changed. That way I could for
instance spot that some array is growing without a valid reason.
Currently I cant think of a way to do this.
Would you be interested in implementing such an idea ?
-Olivier
--
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.
