Open Bug 752467 Opened 13 years ago Updated 2 years ago

Browser window leaked when changing another browser window's windowtype attribute. (browser_580512.js and browser_589246.js)

Categories

(Firefox :: Session Restore, defect)

defect

Tracking

()

People

(Reporter: dao, Unassigned)

References

Details

(Keywords: memory-leak, Whiteboard: [tests disabled in moz15+])

browser_589246.js and browser_580512.js set the host window's windowtype attribute to some random value, do stuff with other windows, and set the windowtype attribute back to navigator:browser. Each of these tests leaks a browser window and I suspect this is due to some code getting confused because the original window suddenly disappears from the set of open windows and later becomes part of it again. We should either disable the tests or fix this behavior if we want to support it.
Ftr, SeaMonkey has not ported these 2 tests.
(In reply to Dão Gottwald [:dao] from comment #0) > browser_589246.js and browser_580512.js set the host window's windowtype > attribute to some random value, do stuff with other windows, and set the > windowtype attribute back to navigator:browser. Each of these tests leaks a > browser window and I suspect this is due to some code getting confused > because the original window suddenly disappears from the set of open windows > and later becomes part of it again. > > We should either disable the tests or fix this behavior if we want to > support it. I'm ok disabling those tests unless a nicer solution can be found. It was a hacky way to trick session restore into thinking there were no browser windows open. Session Restore may even be the source of those leaks. r=me for disabling.
Whiteboard: [tests disabled]
Blocks: 734554
Summary: Browser window leaked when changing another browser window's windowtype attribute → Browser window leaked when changing another browser window's windowtype attribute. (browser_580512.js and browser_589246.js)
Whiteboard: [tests disabled] → [tests disabled in moz15+]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.