ActiveX Browser Memory Leak

[Ludek]

wait, 3?
You mean open and close the window 3 times?

Because that's too little, just leave it there literally a couple o minutes

Yes, open and close the window 3 times => 3 MB leak on Win 7.

Left it for 5 minutes => further 4 MB leak
i.e. 26 KB per attempt in avarage.
It always oscilates between 41MB and 44MB on each attempt and sometimes there is X KB leak, sometimes there isn't.

It is strange that it is indeed Windows 7 related. So it seems to be a leak in Win 7 IE. We use memory manager (for leak detection) in IDE when developing and it doesn't detect the leak.

[ZvezdanD]

I am late for this discussion, but I think I could tell you some observations. I am working on the next version of Tree Report for Child Nodes add-on. The current public implementation is using Web Browser ActiveX with some freeware treeview JavaScript which is called from HTML page. That script is not optimal for large number of nodes, so I want to replace it. I am currently in benchmark phase with several another free treeview Javascripts. One of them has terrible memory leak which raises with number of nodes. I tried with my Location node and its sub-nodes, approx. 20,000 nodes, and I am getting next values for free RAM after closing the dialog box with the ActiveX control: 303 -> 252 -> 227 -> 199 MB. With another two Javascripts that I am trying I don't have such leaks. Testing within Windows XP SP2.

So, maybe you could try your script example with another Web site. Maybe Google which you tried has some Javascript that has leaks. You could take a look at Microsoft article about IE leaks caused by Javascripts: Understanding and Solving Internet Explorer Leak Patterns, also this: JavaScript and memory leaks.

By the way, MM versions older then 3.1.0.1205 had memory leaks after closing dialog boxes, especially with ActiveX controls, even without any Javascripts (I already reported that). To resolve that I am using Script.UnRegisterHandler "wbCtrl_OnChange" and for even older versions which don't have UnRegisterHandler I am using Script.UnRegisterAllEvents, but with it in some cases I need to re-register all needed events again. Unfortunately, UnRegisterHandler and UnRegisterAllEvents cannot resolve problem with the mentioned Javascript that I tried.