-
Notifications
You must be signed in to change notification settings - Fork 22
AccessViolationException #13
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, Aaron!
This is a completely new error. Previously, How often does this error occur? |
We saw it 5 times the day I posted the issue, over about an hour. I have not seen the other |
I can get this consistently on Windows 7 and Windows Server 2012 R2. At the moment I am not seeing it on Windows 10. |
What version of Internet Explorer installed on these machines?
On Windows 10 installed a Microsoft Edge browser, and therefore the MSIE JavaScript Engine working in
I recommend you to read this comment. If you decide to abandon usage of the MSIE JavaScript Engine, then I recommend you to use the JavaScriptEngineSwitcher.ChakraCore. |
My local machine and the server are both IE11 Registering ChakraCore seems to work for me. I had issues trying to do that previously, in case anyone else runs into similar issues, you need to add these packages to your project:
And add this to your Startup.cs You can close this issue if you want, I will be using ChakraCore unless I run into any issues with it, thanks! |
These packages are not needed for Linux and Mac users, therefore everyone should install only necessary packages. About this is written in the documentation and package description. My position about the React.NET is the following - reactjs/React.NET#360 (comment).
I already have the corresponding line - https://github.com/Taritsyn/JavaScriptEngineSwitcher/blob/master/samples/JavaScriptEngineSwitcher.Sample.AspNetCore1.Mvc1/Startup.cs#L56. |
Thanks for the additional information, I guess before I was only checking the React.NET repository. |
I have seen several related issues on different repos but I have not seen this specific one, sorry if this is a duplicate. All the related issues seem to have been solved by updating packages, but I am running the latest I know of.
I am not seeing this issue consistently so I don't know how to reproduce reliably.
I am using:
The text was updated successfully, but these errors were encountered: