-
Notifications
You must be signed in to change notification settings - Fork 49
AccessViolationException in JavaScriptEngineSwitcher.ChakraCore 2.4.3 #30
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
Comments
Hello, Filip!
ChakraCore was updated: 1.4.4 -> 1.5.0. It is possible, that new version of the ChakraCore conflicts with the Chakra from browser (Internet Explorer and Edge). Try to disable usage of the JavaScriptEngineSwitcher.Msie by using the |
Forgot to tell you, i already disable MSIE this way:
|
If you did this after registering the React.NET, then these settings will not have any effect. You just need to insert the following code before registering the React.NET: JsEngineSwitcher.Instance.EngineFactories.AddChakraCore(); And you do not need to remove anything. Which ASP.NET framework do you use? |
Offcourse, this is the order i do it:
I use an ASP.NET MVC Core project with the ASP.NET 4.6.2 framework. |
Then, in your case, it's better to use the following code (read details in the “Registration of JS engines -> ASP.NET Core 1.X” section of documentation): services.AddJsEngineSwitcher()
.AddChakraCore()
; Of course, this will not prevent error, but it would be more correct. |
I replaced the old AddChakraCore(); with the new one. And indeed as expected, it did not fix our problem. Only thing I can do now is try and update Windows. I'll try this soon, when the acceptance server isn't used. |
During half an hour I will publish the fix. |
Try upgrading to version 2.4.4. Packages with native assemblies has not changed. |
It seems to be fixed! |
When i upgrade ChakraCore (incl. native windows packages) to 2.4.3 in my project, the AccessViolationException is back.
Downgrade to 2.4.2 and everything works perfectly.
It seems something has changed in this version, or do i miss something on my server? (like a specific windows update?)
project packages:
The text was updated successfully, but these errors were encountered: