David Baron :dbaron: Assignee
	Description • 20 years ago

When opening and closing tabs, the DOMWINDOW numbers don't go down until the
parent window is closed.  This is a leak that's freed when the containing window
is closed (rather than never freed).

One of the reasons for this (I think there are also some issues with the
browser:purge-session-history observers that I'll file as a separate bug once I
figure out what's going on a little better) is that the focusedWindow member of
the browser binding (which necessarily stays around until the parent window
closes, due to nsDocument::AddReference) is not nulled out.

Patch coming

	David Baron :dbaron: Assignee
	Comment 2 • 20 years ago

I'll add the "so we force a cleanup ourselves" back.  That was inadvertently
dropped.

	Mike Connor [:mconnor]
	Comment 3 • 20 years ago

Comment on attachment 175065 [details] [diff] [review]
patch

r=me, with the comment restored as noted

	David Baron :dbaron: Assignee
	Comment 4 • 20 years ago

Fix checked in to trunk, 2005-02-21 14:50 -0800.

	Oliver Klee
	Comment 5 • 20 years ago

There is a typo in the patch: hapen -> happen