New Post: How to change the Global Object to another object?

January 15, 2014, 7:35 am

≫ Next: New Post: Problem Calling VBScript Function

≪ Previous: New Post: How to change the Global Object to another object?

Hello!

You can't replace the global object, but you can easily set up an alias that will satisfy the above code:

engine.Execute("window = this");

Please let us know if that doesn't work for you.

Thanks!

↧

New Post: Problem Calling VBScript Function

January 15, 2014, 8:33 pm

≫ Next: New Post: Calling VBScript function by dispatchId

≪ Previous: New Post: How to change the Global Object to another object?

Any news on v 5.3.11?

↧

New Post: Calling VBScript function by dispatchId

January 16, 2014, 5:17 am

≫ Next: New Post: Calling VBScript function by dispatchId

≪ Previous: New Post: Problem Calling VBScript Function

Legacy application use with the Clone method of the IActiveScript.
Creating new empty VBScriptEngine is not solution, initializing of the new scripter is not simply.

↧

New Post: Calling VBScript function by dispatchId

January 16, 2014, 5:28 am

≫ Next: Created Feature: Add support for Windows script engine cloning [35]

≪ Previous: New Post: Calling VBScript function by dispatchId

Ah, very interesting. Your legacy application does some advanced Windows Script hosting!

Engine cloning via IActiveScript::Clone is not something that we've investigated. It does sound like a very powerful capability - one that even the mighty V8 does not currently provide. We will definitely add support for it in a future ClearScript release.

Thank you!

↧

Created Feature: Add support for Windows script engine cloning [35]

January 16, 2014, 5:39 am

≫ Next: Source code checked in, #aa16a8a84beab6c094c073061d1f237e58cfa301

≪ Previous: New Post: Calling VBScript function by dispatchId

The `IActiveScript::Clone` method can be used by multithreaded hosts to set up per-thread engine instances. This is a powerful capability that could greatly enhance the use of Windows script engines on the server.

↧

Source code checked in, #aa16a8a84beab6c094c073061d1f237e58cfa301

January 16, 2014, 5:54 am

≫ Next: Edited Feature: Allow custom locations in V8Proxy.GetDirPaths [34]

≪ Previous: Created Feature: Add support for Windows script engine cloning [35]

Version 5.3.11: Added support for building strong named assemblies (see ReadMe.txt), added AppDomain.AssemblyResolve hook for ClearScriptV8 (Issue #34), added WindowsScriptEngineFlags.EnableStandardsMode, fixed parameterless invocation of Windows script items from VB.NET, fixed WindowsScriptEngine execution result variant leak, hardened assembly table I/O (Issue #33), updates for breaking V8 API changes, added tests for bug fixes and new APIs. Tested with V8 3.24.17.

↧

Edited Feature: Allow custom locations in V8Proxy.GetDirPaths [34]

January 16, 2014, 6:01 am

≫ Next: Commented Feature: Allow custom locations in V8Proxy.GetDirPaths [34]

≪ Previous: Source code checked in, #aa16a8a84beab6c094c073061d1f237e58cfa301

I am bundling the ClearScript DLLs as embedded resources in my main application/dll. At runtime I extract ClearScriptV8-XX.dll and v8-xXX.dll to a temporary path (typically Temporary ASP.NET Files) so that they can be loaded from disk.

In order to support this I have added a simple static API which allows adding custom locations returned by V8Proxy.GetDirPaths. It would be ideal if some equivalent functionality were included in the library.

This issue is somewhat related to https://clearscript.codeplex.com/workitem/17

↧

Commented Feature: Allow custom locations in V8Proxy.GetDirPaths [34]

January 16, 2014, 6:01 am

≫ Next: Edited Issue: Administrator rights [33]

≪ Previous: Edited Feature: Allow custom locations in V8Proxy.GetDirPaths [34]

↧

Edited Issue: Administrator rights [33]

January 16, 2014, 6:02 am

≫ Next: Commented Issue: Administrator rights [33]

≪ Previous: Commented Feature: Allow custom locations in V8Proxy.GetDirPaths [34]

When attempting to run in low rights mode I found that the service was unable to access (or possibly create) a folder in the %appdata%/local/microsoft/clearscript/(x64|x86)/(.net version). It seems to create a file called AssemblyTable.bin in that folder. Is it necessary? Is there any way to avoid this and not require administrative access?

For specifics I'm running this on a server using the AppPoolIdentity. I set the apppool to run under administrator for the first time and then back to apppoolidentity and it works fine.

I'm not sure what the issue issue just yet but wondering if this is a known issue or not. Couldn't find anything in the issues here on codeplex.

↧

Commented Issue: Administrator rights [33]

January 16, 2014, 6:02 am

≫ Next: Updated Release: ClearScript 5.3 (May 21, 2013)

≪ Previous: Edited Issue: Administrator rights [33]

↧

Updated Release: ClearScript 5.3 (May 21, 2013)

January 16, 2014, 6:06 am

≫ Next: Updated Wiki: Announcements

≪ Previous: Commented Issue: Administrator rights [33]

5.3.11

Added support for building strong named assemblies (see ReadMe.txt).
Added AppDomain.AssemblyResolve hook for ClearScriptV8 (Issue #34).
Added WindowsScriptEngineFlags.EnableStandardsMode.
Fixed parameterless invocation of Windows script items from VB.NET.
Fixed WindowsScriptEngine execution result variant leak.
Hardened assembly table I/O (Issue #33).
Updates for breaking V8 API changes.
Added tests for bug fixes and new APIs.
Tested with V8 3.24.17.

5.3.10

Added support for Visual Studio 2013.
Fixed ErrorDetails line number issue in WindowsScriptEngine (Issue #24).
Added ScriptEngine.FormatCode and V8Runtime.FormatCode.
Code formatting is now disabled by default.
Fixed script access to nullable values (Issue #30).
Added ScriptEngine.GetStackTrace() (Issue #27).
Added V8Runtime.MaxStackUsage and V8ScriptEngine.MaxRuntimeStackUsage (Issue #26).
Fixed V8 root object marshaling crash when GlobalMembers is in effect.
Added tests for bug fixes and new APIs.
Tested with V8 3.23.13.

5.3.9

V8Update now fetches known-good versions of GYP, Python, and Cygwin (Issue #20).
Fixed HostMethod and HostIndexedProperty arguments.
Added tests for bug fixes.
Tested with V8 3.22.23.

5.3.8

Added dynamic host object projection (Issue #3).
Added support for overloaded indexers and indexed properties.
Interface targets now expose System.Object members.
Expanded caching for improved performance and memory usage.
Fixed crashes and deadlocks when shutting down with Eclipse debugger attached.
Added support for custom preloading of auxiliary assemblies (Issue #17).
Added many new tests.
Migrated to new V8 Persistent API.
Tested with V8 3.22.11.

5.3.7

Fixed V8ScriptEngine compiled script evaluation result marshaling (Issue #16).
Added a test for the fix.
Cleared PYTHONPATH in V8Update.
Tested with V8 3.21.2.

5.3.6

Added numeric conversion methods in HostFunctions.
Fixed bugs affecting numeric arguments and return values.
Added tests for bug fixes and new APIs.
Tested with V8 3.20.16.

5.3.5

Fixed invocation of base interface methods on derived interface targets (Issue #14).
Fixed V8 and ClearScript builds on certain non-English locales (Issue #13).
Added boxed enum reference canonicalization (Issue #15).
PropertyBag enhancements.
Lots of minor host integration fixes.
Updates for breaking V8 API changes.
Several new tests.
Tested with V8 3.20.12.

5.3.4

Fixed script interruption crash in V8ScriptEngine.
Added a test for the fix.

5.3.3

Improved V8 error handling (Issue #12).
Lowered .NET Framework target to v4.0.
Added several tests.
Tested with V8 3.19.18.

5.3.2

Updates for breaking V8 API changes.
V8Update now fetches a tested revision by default.
Tested with V8 3.19.9.

5.3.1

Fixed JScriptEngine dynamic binding bug (Issue #9).

5.3.0

Enhancements for V8 users:
- V8ScriptEngine now supports script compilation and re-execution.
- New V8Runtime class allows engines to share resources and compiled scripts.
- New experimental APIs for restricting and querying V8 memory usage.
- Improved V8 loading algorithm for simplified deployment.
- V8Update can now fetch a V8 version that is known to work with ClearScript.
New method: ScriptEngine.CollectGarbage().
Host item caching improves performance and reduces memory usage.
Several new tests.

↧

Updated Wiki: Announcements

January 16, 2014, 6:13 am

≫ Next: Updated Wiki: Documentation

≪ Previous: Updated Release: ClearScript 5.3 (May 21, 2013)

1/16/2014: Version 5.3.11 released.

View the release notes and download the source code here.

11/28/2013: Version 5.3.10 released.

View the release notes and download the source code here.

10/29/2013: Version 5.3.9 released.

View the release notes and download the source code here.

10/14/2013: Version 5.3.8 released.

View the release notes and download the source code here.

8/22/2013: Version 5.3.7 released.

View the release notes and download the source code here.

8/14/2013: Version 5.3.6 released.

View the release notes and download the source code here.

8/2/2013: Version 5.3.5 released.

View the release notes and download the source code here.

7/10/2013: Version 5.3.4 released.

View the release notes and download the source code here.

7/2/2013: Version 5.3.3 released.

View the release notes and download the source code here.

6/6/2013: Version 5.3.2 released.

View the release notes and download the source code here. Due to issues with several recent V8 trunk releases (build failures, breaking API changes, etc.), and because more breaking changes are coming soon, this release modifies V8Update so that it fetches a tested, known-good V8 revision by default. See the ClearScript ReadMe for more information.

5/31/2013: Version 5.3.1 released.

View the release notes and download the source code here.

5/21/2013: ClearScript 5.3 released.

View the release notes and download the source code here.

5/15/2013: Version 5.2.2 released.

View the release notes and download the source code here. This release addresses the build issue reported yesterday and can be used with the latest V8 version. Here's how to update your copy of V8:

C:\ClearScript> set V8REV=
C:\ClearScript> V8Update

5/14/2013: ClearScript build failure due to API deprecation in V8 3.19.1.

We are aware of a ClearScript build issue with the latest version of V8. Until this issue is resolved we recommend that you explicitly use V8 3.19.0:

C:\ClearScript> set V8REV=14604
C:\ClearScript> V8Update

5/2/2013: Version 5.2.1 released.

View the release notes and download the source code here.

4/18/2013: V8Update failure resolved by V8 3.18.1.

The V8Update issue reported yesterday has been fixed by a new version of V8 released today. Here's how to update to the latest V8 version:

C:\ClearScript> set V8REV=
C:\ClearScript> V8Update

4/17/2013: V8Update failure with V8 3.18.0.

We are aware of a V8Update issue with the latest version of V8. Until this issue is resolved we recommend that you explicitly use V8 3.17.16:

C:\ClearScript> set V8REV=14138
C:\ClearScript> V8Update

3/27/2013: ClearScript 5.2 released.

View the release notes and download the source code here.

3/8/2013: Version 5.1.3 released.

View the release notes and download the source code here.

3/4/2013: V8Update failure resolved by V8 3.17.7.

The V8Update issue reported earlier has been fixed by a new version of V8 released today. Here's how to update to the latest V8 version:

C:\ClearScript> set V8REV=
C:\ClearScript> V8Update

3/4/2013: V8Update failure with V8 3.17.6.

We are aware of a V8Update issue with the latest version of V8. The issue affects the "Building 64-bit V8" step. The V8 team appears to have already submitted a fix, but the fix has not yet been merged into the trunk. In the meantime, we recommend that you explicitly use V8 3.17.5:

C:\ClearScript> set V8REV=13745
C:\ClearScript> V8Update

↧

Updated Wiki: Documentation

January 16, 2014, 6:13 am

≫ Next: Updated Wiki: Home

≪ Previous: Updated Wiki: Announcements

Documentation

To learn more about ClearScript:

Check out the ClearScript tutorial: [Word], [PDF].
Browse the ClearScript Library Reference: [Cannot resolve file macro, invalid file name or id.]. Save this file before opening it. If you get a security warning when you open it, uncheck "Always ask before opening this file".
View the latest information in the ClearScript ReadMe.
Take a look at our latest Announcements.

↧

Updated Wiki: Home

January 16, 2014, 6:15 am

≫ Next: New Post: Problem Calling VBScript Function

≪ Previous: Updated Wiki: Documentation

Version 5.3.11 released. More...

Description

ClearScript is a library that makes it easy to add scripting to your .NET applications. It currently supports JavaScript (via V8 and JScript) and VBScript.

Features

Simple usage; create a script engine, add your objects and/or types, run scripts
Support for several script engines: Google's V8, Microsoft's JScript and VBScript
Exposed resources require no modification, decoration, or special coding of any kind
Scripts get simple access to most of the features of exposed objects and types:
- Methods, properties, fields, events
- (Objects) Indexers, extension methods, conversion operators, explicitly implemented interfaces
- (Types) Constructors, nested types
Full support for generic types and methods, including C#-like type inference and explicit type arguments
Scripts can invoke methods with output parameters, optional parameters, and parameter arrays
Script delegates enable callbacks into script code
Support for exposing all the types defined in one or more assemblies in one step
Optional support for importing types and assemblies from script code
The host can invoke script functions and access script objects directly
Full support for script debugging

Examples

using System;
using Microsoft.ClearScript;
using Microsoft.ClearScript.V8;

// create a script engineusing (var engine = new V8ScriptEngine())
{
    // expose a host type
    engine.AddHostType("Console", typeof(Console));
    engine.Execute("Console.WriteLine('{0} is an interesting number.', Math.PI)");

    // expose a host object
    engine.AddHostObject("random", new Random());
    engine.Execute("Console.WriteLine(random.NextDouble())");

    // expose entire assemblies
    engine.AddHostObject("lib", new HostTypeCollection("mscorlib", "System.Core"));
    engine.Execute("Console.WriteLine(lib.System.DateTime.Now)");

    // create a host object from script
    engine.Execute(@"
        birthday = new lib.System.DateTime(2007, 5, 22);
        Console.WriteLine(birthday.ToLongDateString());
    ");

    // use a generic class from script
    engine.Execute(@"
        Dictionary = lib.System.Collections.Generic.Dictionary;
        dict = new Dictionary(lib.System.String, lib.System.Int32);
        dict.Add('foo', 123);
    ");

    // call a host method with an output parameter
    engine.AddHostObject("host", new HostFunctions());
    engine.Execute(@"
        intVar = host.newVar(lib.System.Int32);
        found = dict.TryGetValue('foo', intVar.out);
        Console.WriteLine('{0} {1}', found, intVar);
    ");

    // create and populate a host array
    engine.Execute(@"
        numbers = host.newArr(lib.System.Int32, 20);
        for (var i = 0; i < numbers.Length; i++) { numbers[i] = i; }
        Console.WriteLine(lib.System.String.Join(', ', numbers));
    ");

    // create a script delegate
    engine.Execute(@"
        Filter = lib.System.Func(lib.System.Int32, lib.System.Boolean);
        oddFilter = new Filter(function(value) {
            return (value & 1) ? true : false;
        });
    ");

    // use LINQ from script
    engine.Execute(@"
        oddNumbers = numbers.Where(oddFilter);
        Console.WriteLine(lib.System.String.Join(', ', oddNumbers));
    ");

    // use a dynamic host object
    engine.Execute(@"
        expando = new lib.System.Dynamic.ExpandoObject();
        expando.foo = 123;
        expando.bar = 'qux';
        delete expando.foo;
    ");

    // call a script function
    engine.Execute("function print(x) { Console.WriteLine(x); }");
    engine.Script.print(DateTime.Now.DayOfWeek);

    // examine a script object
    engine.Execute("person = { name: 'Fred', age: 5 }");
    Console.WriteLine(engine.Script.person.name);
}

↧

New Post: Problem Calling VBScript Function

January 16, 2014, 6:17 am

≫ Next: Updated Wiki: Documentation

≪ Previous: Updated Wiki: Home

The source code for Version 5.3.11 is now up. Cheers!

↧

Updated Wiki: Documentation

January 16, 2014, 6:19 am

≫ Next: Released: ClearScript 5.3 (May 21, 2013)

≪ Previous: New Post: Problem Calling VBScript Function

Documentation

To learn more about ClearScript:

Check out the ClearScript tutorial: [Word], [PDF].
Browse the ClearScript Library Reference: [Reference.chm]. Save this file before opening it. If you get a security warning when you open it, uncheck "Always ask before opening this file".
View the latest information in the ClearScript ReadMe.
Take a look at our latest Announcements.

↧

Released: ClearScript 5.3 (May 21, 2013)

January 16, 2014, 6:24 am

≫ Next: Updated Release: ClearScript 5.3 (May 21, 2013)

≪ Previous: Updated Wiki: Documentation

5.3.11

Added support for building strong named assemblies (see ReadMe.txt).
Added AppDomain.AssemblyResolve hook for ClearScriptV8 (Issue #34).
Added WindowsScriptEngineFlags.EnableStandardsMode.
Fixed parameterless invocation of Windows script items from VB.NET.
Fixed WindowsScriptEngine execution result variant leak.
Hardened assembly table I/O (Issue #33).
Updates for breaking V8 API changes.
Added tests for bug fixes and new APIs.
Tested with V8 3.24.17.

5.3.10

Added support for Visual Studio 2013.
Fixed ErrorDetails line number issue in WindowsScriptEngine (Issue #24).
Added ScriptEngine.FormatCode and V8Runtime.FormatCode.
Code formatting is now disabled by default.
Fixed script access to nullable values (Issue #30).
Added ScriptEngine.GetStackTrace() (Issue #27).
Added V8Runtime.MaxStackUsage and V8ScriptEngine.MaxRuntimeStackUsage (Issue #26).
Fixed V8 root object marshaling crash when GlobalMembers is in effect.
Added tests for bug fixes and new APIs.
Tested with V8 3.23.13.

5.3.9

V8Update now fetches known-good versions of GYP, Python, and Cygwin (Issue #20).
Fixed HostMethod and HostIndexedProperty arguments.
Added tests for bug fixes.
Tested with V8 3.22.23.

5.3.8

Added dynamic host object projection (Issue #3).
Added support for overloaded indexers and indexed properties.
Interface targets now expose System.Object members.
Expanded caching for improved performance and memory usage.
Fixed crashes and deadlocks when shutting down with Eclipse debugger attached.
Added support for custom preloading of auxiliary assemblies (Issue #17).
Added many new tests.
Migrated to new V8 Persistent API.
Tested with V8 3.22.11.

5.3.7

Fixed V8ScriptEngine compiled script evaluation result marshaling (Issue #16).
Added a test for the fix.
Cleared PYTHONPATH in V8Update.
Tested with V8 3.21.2.

5.3.6

Added numeric conversion methods in HostFunctions.
Fixed bugs affecting numeric arguments and return values.
Added tests for bug fixes and new APIs.
Tested with V8 3.20.16.

5.3.5

Fixed invocation of base interface methods on derived interface targets (Issue #14).
Fixed V8 and ClearScript builds on certain non-English locales (Issue #13).
Added boxed enum reference canonicalization (Issue #15).
PropertyBag enhancements.
Lots of minor host integration fixes.
Updates for breaking V8 API changes.
Several new tests.
Tested with V8 3.20.12.

5.3.4

Fixed script interruption crash in V8ScriptEngine.
Added a test for the fix.

5.3.3

Improved V8 error handling (Issue #12).
Lowered .NET Framework target to v4.0.
Added several tests.
Tested with V8 3.19.18.

5.3.2

Updates for breaking V8 API changes.
V8Update now fetches a tested revision by default.
Tested with V8 3.19.9.

5.3.1

Fixed JScriptEngine dynamic binding bug (Issue #9).

5.3.0

Enhancements for V8 users:
- V8ScriptEngine now supports script compilation and re-execution.
- New V8Runtime class allows engines to share resources and compiled scripts.
- New experimental APIs for restricting and querying V8 memory usage.
- Improved V8 loading algorithm for simplified deployment.
- V8Update can now fetch a V8 version that is known to work with ClearScript.
New method: ScriptEngine.CollectGarbage().
Host item caching improves performance and reduces memory usage.
Several new tests.

↧

Updated Release: ClearScript 5.3 (May 21, 2013)

January 16, 2014, 6:24 am

≫ Next: New Post: IIS Express is OK . But in Local IIS error: " Can not load assembly V8 interface ... " . Why ?

≪ Previous: Released: ClearScript 5.3 (May 21, 2013)

5.3.11

Added support for building strong named assemblies (see ReadMe.txt).
Added AppDomain.AssemblyResolve hook for ClearScriptV8 (Issue #34).
Added WindowsScriptEngineFlags.EnableStandardsMode.
Fixed parameterless invocation of Windows script items from VB.NET.
Fixed WindowsScriptEngine execution result variant leak.
Hardened assembly table I/O (Issue #33).
Updates for breaking V8 API changes.
Added tests for bug fixes and new APIs.
Tested with V8 3.24.17.

5.3.10

Added support for Visual Studio 2013.
Fixed ErrorDetails line number issue in WindowsScriptEngine (Issue #24).
Added ScriptEngine.FormatCode and V8Runtime.FormatCode.
Code formatting is now disabled by default.
Fixed script access to nullable values (Issue #30).
Added ScriptEngine.GetStackTrace() (Issue #27).
Added V8Runtime.MaxStackUsage and V8ScriptEngine.MaxRuntimeStackUsage (Issue #26).
Fixed V8 root object marshaling crash when GlobalMembers is in effect.
Added tests for bug fixes and new APIs.
Tested with V8 3.23.13.

5.3.9

V8Update now fetches known-good versions of GYP, Python, and Cygwin (Issue #20).
Fixed HostMethod and HostIndexedProperty arguments.
Added tests for bug fixes.
Tested with V8 3.22.23.

5.3.8

Added dynamic host object projection (Issue #3).
Added support for overloaded indexers and indexed properties.
Interface targets now expose System.Object members.
Expanded caching for improved performance and memory usage.
Fixed crashes and deadlocks when shutting down with Eclipse debugger attached.
Added support for custom preloading of auxiliary assemblies (Issue #17).
Added many new tests.
Migrated to new V8 Persistent API.
Tested with V8 3.22.11.

5.3.7

Fixed V8ScriptEngine compiled script evaluation result marshaling (Issue #16).
Added a test for the fix.
Cleared PYTHONPATH in V8Update.
Tested with V8 3.21.2.

5.3.6

Added numeric conversion methods in HostFunctions.
Fixed bugs affecting numeric arguments and return values.
Added tests for bug fixes and new APIs.
Tested with V8 3.20.16.

5.3.5

Fixed invocation of base interface methods on derived interface targets (Issue #14).
Fixed V8 and ClearScript builds on certain non-English locales (Issue #13).
Added boxed enum reference canonicalization (Issue #15).
PropertyBag enhancements.
Lots of minor host integration fixes.
Updates for breaking V8 API changes.
Several new tests.
Tested with V8 3.20.12.

5.3.4

Fixed script interruption crash in V8ScriptEngine.
Added a test for the fix.

5.3.3

Improved V8 error handling (Issue #12).
Lowered .NET Framework target to v4.0.
Added several tests.
Tested with V8 3.19.18.

5.3.2

Updates for breaking V8 API changes.
V8Update now fetches a tested revision by default.
Tested with V8 3.19.9.

5.3.1

Fixed JScriptEngine dynamic binding bug (Issue #9).

5.3.0

Enhancements for V8 users:
- V8ScriptEngine now supports script compilation and re-execution.
- New V8Runtime class allows engines to share resources and compiled scripts.
- New experimental APIs for restricting and querying V8 memory usage.
- Improved V8 loading algorithm for simplified deployment.
- V8Update can now fetch a V8 version that is known to work with ClearScript.
New method: ScriptEngine.CollectGarbage().
Host item caching improves performance and reduces memory usage.
Several new tests.

↧

New Post: IIS Express is OK . But in Local IIS error: " Can not load assembly V8 interface ... " . Why ?

January 16, 2014, 6:53 am

≫ Next: Commented Issue: [V8 bug] Issue with memory leaking scripts: 5.3.9 vs 5.3.10 [32]

≪ Previous: Updated Release: ClearScript 5.3 (May 21, 2013)

I installed the above file, rebooted the PC and problem persists.

I have already had laying around here installed, Visual Studio 2013.

Remembering that when I access the site with IIS Express is transforming the files correctly.

The error only occurs with the Local IIS and server (smarterasp.net) too.

Any idea, what can this missing?

↧

Commented Issue: [V8 bug] Issue with memory leaking scripts: 5.3.9 vs 5.3.10 [32]

January 16, 2014, 8:48 am

≫ Next: New Post: IIS Express is OK . But in Local IIS error: " Can not load assembly V8 interface ... " . Why ?

≪ Previous: New Post: IIS Express is OK . But in Local IIS error: " Can not load assembly V8 interface ... " . Why ?

Hi everybody,

I just noticed a behavior that differs between ClearScript v 5.3.9 and 5.3.10, and it's about limiting memory for a script execution. Consider following faulty script (it emulates a memory leak) being executed inside the 64 bit console application:
```
var sample_arr = [-1, 5, 7, 4, 0, 1, -5]
function My_Partition(container, first_index, last_index) {
var x = container[last_index];
var i = first_index - 1;

for (var elem = 0; elem < container.length-1; elem++) {
if (container[elem] <= x) {
i += 1;
var temp_1 = container[i];
container[i] = container[elem];
container[elem] = temp_1;
}
}
var temp_2 = container[i+1];
container[i+1] = container[last_index];
container[last_index] = temp_2;

return i+1;
}
function My_Quick_Sort(container, first_index, last_index) {
if (first_index < last_index) {
var mid = My_Partition(container, first_index, last_index);
My_Quick_Sort(container, first_index, mid-1);
My_Quick_Sort(container, mid+1, last_index);
}
}
My_Quick_Sort(sample_arr, 0, sample_arr.length-1);
console.WriteLine("Sorted Array:", sample_arr);
```
as well as following ClearScript's V8 engine configuration:
```
Using engine As New V8ScriptEngine("V8Engine", New V8RuntimeConstraints() With {.MaxOldSpaceSize = 209715200}, V8ScriptEngineFlags.EnableDebugging, 9222)
```
You'll notice that after running above code in 5.3.9 it gracefully ends up with an exception that indicates a memory limit being exceeded (see attachment). However, in 5.3.10 it doesn't result in exception and rather hard-crashes with a message in the console (see attachment). Could you test it on your end and provide some follow-up?

System used for testing: Window 7, 64 bit.

Thanks for your work,
Max

Comments: Thanks for following this one up closely, keep us posted.

↧