In version 5.4.7 and 5.4.8 there's still a memory leak related to script evaluations with the VBScriptEngine.
I've attached a test project, where 1000 predefined equations can be evaluated with VBScriptEngine or with the V8 engine. When re-evaluating the equations with V8 engine, the used process memory keeps stable, but not with the VBScriptEnginge. It seems to be an unmanaged memory leak.
To run the attached test project properly, ClearScript has to be added via nuget first.
Comments: I made my tests with the VBScriptEngine and the V8 engine by using the ClearScript.V8 nuget package in version 5.4.7 under Windows 7 Pro x64. So, I started the test application and clicked 50 times on the button "Test VB-Script", respectively the "Test V8" button and watchted the used "process memory" in the diagnostics tools in Visual Studio. I have attached two screenshots from my tests. As you can see, the used process memory when using the V8 engine keeps stable, but not for VBScript engine. In my real world application there're also evaluated hundreds of scripts hundereds of times at runtime and it would be very nice to fix this issue. Best regards.
I've attached a test project, where 1000 predefined equations can be evaluated with VBScriptEngine or with the V8 engine. When re-evaluating the equations with V8 engine, the used process memory keeps stable, but not with the VBScriptEnginge. It seems to be an unmanaged memory leak.
To run the attached test project properly, ClearScript has to be added via nuget first.
Comments: I made my tests with the VBScriptEngine and the V8 engine by using the ClearScript.V8 nuget package in version 5.4.7 under Windows 7 Pro x64. So, I started the test application and clicked 50 times on the button "Test VB-Script", respectively the "Test V8" button and watchted the used "process memory" in the diagnostics tools in Visual Studio. I have attached two screenshots from my tests. As you can see, the used process memory when using the V8 engine keeps stable, but not for VBScript engine. In my real world application there're also evaluated hundreds of scripts hundereds of times at runtime and it would be very nice to fix this issue. Best regards.