When using the DOM way of accessing the document, i get _huge_ memory leaks of over 170 megabytes, but when the HTML is something called 'well formed' (XML term), it leaks less, but still it leaks unbelieavably much.

I haven't run purify in the last week or so, but prior to that I didn't see "enormous" memory leaks. I'll try again in the next couple of days, but please provide a test case. Since not much has changed in the last week, I don't think I will see the leak that you mention with my DOM tests.

Here are the test cases, I had to modify them not to include some private book- marks, but the leak is still big.

Putting on ss: radar.

This is not a ss bug. I'm looking into it, but the DOM as a whole is not the cause of memory leaks in the general case. I'm taking it off the ss: radar.

Setting all current Open Critical and Major to M3

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

Still trying to create the memory leak and I can't. There is a problem with the testcast, however: the function processChildren() references node.lastChild.nodeType even if node is a Text node. The value of node.lastChild in this case would be null and the attempt to get the nodeType property fails. This is a fairly old bug, so I'd like to assume that any earlier problems seen have been resolved. Please tell me if this is no longer true.

jty, please verify resolution is correct. Otherwise I'll have to close this bug.

Bug closed.

Revised delivery date 07/21