| Index: LayoutTests/fast/dom/Window/property-access-on-cached-window-after-frame-removed-and-gced.html | 
| diff --git a/LayoutTests/fast/dom/Window/property-access-on-cached-window-after-frame-removed-and-gced.html b/LayoutTests/fast/dom/Window/property-access-on-cached-window-after-frame-removed-and-gced.html | 
| index e89c4628383cb99003a0628b53d11b3202e087c1..56a771f9db31677818b331edee192c5c98d88970 100644 | 
| --- a/LayoutTests/fast/dom/Window/property-access-on-cached-window-after-frame-removed-and-gced.html | 
| +++ b/LayoutTests/fast/dom/Window/property-access-on-cached-window-after-frame-removed-and-gced.html | 
| @@ -19,7 +19,8 @@ function runTest() | 
| description("Tests property access on a cached DOMWindow after the associated frame is removed from a web page and garbage collected. Test should not crash and properties should be set to sane defaults."); | 
| var frame = document.getElementById("frame"); | 
| childWindow = frame.contentWindow; | 
| -    collectProperties(); | 
| +    // Have expected results assume that the frame has been GCed (=> window.closed = true.) | 
| +    collectProperties(true); | 
| frame.parentNode.removeChild(frame); | 
| window.setTimeout(verifyResults, 0); | 
| } | 
|  |