P
Phil Barker
A memory leak seems to occur when the following steps are
followed:
1) An IE window (window A) is opened from shortcut/etc..
2) A second IE window (window B) running an ActiveX
component is launched from window A via a Javascript
window.open call
3) window B is closed
The memory used by window B (and indeed the ActiveX
component) are not released as expected at step 3.
Instead the memory seems to be held until the parent
window A itself is closed.
There are several notes on similar problems, but most
seem to give the impression that they are addressed
within IE 5.01. Since the problem is present in IE 6
(after all current patches have been applied) I'm
interested in whether anyone else has experienced this
problem or found a solution.
Thanks,
Phil
followed:
1) An IE window (window A) is opened from shortcut/etc..
2) A second IE window (window B) running an ActiveX
component is launched from window A via a Javascript
window.open call
3) window B is closed
The memory used by window B (and indeed the ActiveX
component) are not released as expected at step 3.
Instead the memory seems to be held until the parent
window A itself is closed.
There are several notes on similar problems, but most
seem to give the impression that they are addressed
within IE 5.01. Since the problem is present in IE 6
(after all current patches have been applied) I'm
interested in whether anyone else has experienced this
problem or found a solution.
Thanks,
Phil