-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cyclic dependency throws System.AccessViolationException from V8 #181
Comments
Here is a more complete stack trace:
And a more correct exception:
|
Hi @DarkfireHellspawn, Thanks for reporting the crash. We're investigating. By the way, instead of loading and patching the file, you can simply do this: engine.ExecuteDocument("js/run.js", ModuleCategory.Standard); Cheers! |
The next ClearScript release will include a fix for this issue. Thanks again! |
Hi, Thanks for the fix! Any idea when it will be available? Thanks, |
Hi Mike, It looks like V8 8.3 is scheduled to go stable in a few days. Hopefully we can get a release out about a week after that. Thanks! |
…; added JavaScriptExtensions.ToTask (GitHub Issue #182); added DocumentLoader.MaxCacheSize and DocumentCategory.MaxCacheSize; added code to break event connections on engine disposal (GitHub Issue #183); improved ES6 module support, fixing cycle crash (GitHub Issue #181); added DynamicHostObject (GitHub Issue #180); added BigInt / BigInteger support for V8 (GitHub Issue #176); hardened Assembly.Load call in V8Proxy.cs (GitHub Issue #175); improved V8Update environment isolation to fix some V8 build issues (GitHub Issue #185); updated API documentation. Tested with V8 8.3.110.9.
Fixed in Version 6.0.2. |
Hi,
If I have a super class, such as:
And a child class:
And a global file to run:
With a .NET Core 3.1 Console Application:
When I run, I receive:
And the stack trace:
Any help will be appreciated.
Thanks,
Mike
The text was updated successfully, but these errors were encountered: