Skip to content
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.

simple run Error #112

Open
DavidDXY opened this issue Jun 9, 2020 · 6 comments
Open

simple run Error #112

DavidDXY opened this issue Jun 9, 2020 · 6 comments

Comments

@DavidDXY
Copy link

DavidDXY commented Jun 9, 2020

when the app load the html url ,throw this error:
System.AccessViolationException:“Attempted to read or write protected memory. This is often an indication that other memory is corrupt.”

@nmocruz
Copy link

nmocruz commented Jun 13, 2020

I have this one to.

@nmocruz
Copy link

nmocruz commented Jun 14, 2020

@DavidDXY I solved it on the samples just changing the target to x64. I have also installed the Edge Chromium beta, not sure if any other dependency was important.

@DapperDeer
Copy link

DapperDeer commented Aug 13, 2020

I believe that this is being caused by a missing file: blazor.desktop.js which is what wwwroot/index.html is trying to call, but there is no js file associated with the sample. I'm not sure if it's supposed to be generated during build, but I do believe this is what's causing the error.

Edit: Nope, I'm incorrect. Removing the line still comes up with the memory error and its referenced throughout other Blazor pages. I just installed the new Edge and changed the target to x64, still with no luck.

@igor-lukashenya
Copy link

I believe that this is being caused by a missing file: blazor.desktop.js which is what wwwroot/index.html is trying to call, but there is no js file associated with the sample. I'm not sure if it's supposed to be generated during build, but I do believe this is what's causing the error.

Edit: Nope, I'm incorrect. Removing the line still comes up with the memory error and its referenced throughout other Blazor pages. I just installed the new Edge and changed the target to x64, still with no luck.

Do yo resolve this issue?

@DapperDeer
Copy link

Do yo resolve this issue?

Yes, actually. I fixed this issue by downloading Edge Insider .

@devbf
Copy link

devbf commented Sep 30, 2020

Had the same issue, solved it by adding this SDK via NuGet.
This article helped me resolving this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants