Skip to content
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

throw System.AccessViolationException from edge.js 8.2.1 #581

Closed
simpleway2016 opened this issue Aug 11, 2017 · 11 comments
Closed

throw System.AccessViolationException from edge.js 8.2.1 #581

simpleway2016 opened this issue Aug 11, 2017 · 11 comments

Comments

@simpleway2016
Copy link

if i use edge.js in wpf application,it works.
but i use edge.js in UnitTest project,it throw System.AccessViolationException

@simpleway2016 simpleway2016 changed the title System.AccessViolationException from version 8.2.1 System.AccessViolationException from edge.js 8.2.1 Aug 11, 2017
@simpleway2016 simpleway2016 changed the title System.AccessViolationException from edge.js 8.2.1 throw System.AccessViolationException from edge.js 8.2.1 Aug 11, 2017
@mmanela
Copy link

mmanela commented Aug 26, 2017

I have the same issue. Was trying to use it in my integration unit tests and I get this exception.

@OndraM-Kentico
Copy link

I'm experiencing the same exception with test project (NUnit) and edge.js v8.2.1:
System.AccessViolationException was unhandled Message: An unhandled exception of type 'System.AccessViolationException' occurred in edge_nativeclr.node Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
When the code in run console app, no exception occurs. I'd very appreciate if it was fixed as the issue makes edge.js completely unusable.

@agracio
Copy link
Collaborator

agracio commented Sep 18, 2017

The fix requires #573 pull request to be merged. There is some more discussion on this thread: #586

@zenglo
Copy link

zenglo commented Nov 14, 2017

I also encountered this problem, it encountered in the asp.net mvc, I indirectly through a console program calls the edge, to circumvent the AccessViolationException, I wrote a demo, if you want to know, can see EdgeJsDemo. Of course, the hope is that author can fundamentally solve the problem.

@agracio
Copy link
Collaborator

agracio commented Nov 14, 2017

The fix requires #573, I have merged it to my fork at https://github.com/agracio/edge-js, take a look at #586 for reference.

@OndraM-Kentico
Copy link

Unfortunately, in my NUnit tests project, I haven't managed to make it work with pre-compiled binaries. @agracio , could you provide NuGet package, please?

@agracio
Copy link
Collaborator

agracio commented Dec 23, 2017

I know its been over a month, but I have finally published NuGet packages for https://github.com/agracio/edge-js fork. Take a look at release page for details https://github.com/agracio/edge-js/releases.
Direct link to NuGet release.

@fforjan
Copy link

fforjan commented Jan 4, 2018

@agracio is your fork become a official release ? because I see more update on your branch than here

@agracio
Copy link
Collaborator

agracio commented Jan 4, 2018

It is not official, however @tjanczuk is no longer active on this project and did not provide any updates about its future. I have not attempted to contact him myself, but I understand that noone had any luck. Since he is active on other projects it is not clear why he ignores this one.
Initially I forked this repo to address a blocking issue with some of our apps, but now it became one of my main home projects.
Incidentally there is some discussion about this particular issue as the fix does not appear to work for all users, you might want to take a look: agracio/edge-js#17

@SpicySyntax
Copy link

@agracio I am still having this exact issue when running NUnit tests. Has there been any progress made in this effort?

@agracio
Copy link
Collaborator

agracio commented Dec 25, 2018

This PR is merged to https://github.com/agracio/edge-js

@agracio agracio closed this as completed Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants