A new browser memory stress test has been created that indefinitely adds and removes very large incremental updates in the browser.
(Sam) Results after running overnight on latest trunk (approx. rev #:15588):
ff2 - started at 39872K and this morning shows "network connection error" and memory usage is 42345K
ie6 - virtual pc run out of memory (ie6 is the only application running and virtual pc has 512M pre-allocated memory)
ie7 - started at 33704K and this morning shows "network connection error" and memory usage is 225776K but when trying to close it, it is rocketing to 1.1G
(Jacky) Results for 1.6.2:
FF2 - Started at 34,972K this morning at 29,712K but showed 'Network Connection Error' message
IE7 - Started at 37,256K this morning at 9,072K and showed 'Server Internal Error' message. When trying to close browser, memory usage shot up to about 888MB before slowly decreasing. Took 2 minutes for the actual browser to close.
IE6 - The virtual pc restarted (out of memory).
It appears that this test fails to release a substantial portion of the browser memory associated with the elements being updated by the bridge until the viewport itself is closed.
attached test application