Forums Bug Reports COM memory leak

In the example, the result isn't used by the mSL. I stopped coding the example at the first point inwhich mIRC's memory consumption balloons.

The invocation of the Eval method begins the ballooning of mIRC's memory consumption even though the result of the call is discarded. Furthermore, closing the MSScriptControl com that the eval method was called against does NOT free the memory.

This is different from doing the same thing under cscript.exe which causes cscript.exe to max at 30-40mb regardless of number of calls against the MSScriptControl instance's Eval method.


If need be I can write a more fleshed-out script and provide the cscript.exe equivalent to help you further understand/trace the issue