Skip to content

[Linux: Pop_OS 22.04] Updated dotnet-script and am getting Fatal error. Internal CLR error. (0x80131506) #685

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

Closed
MostHated opened this issue Sep 25, 2022 · 3 comments

Comments

@MostHated
Copy link

MostHated commented Sep 25, 2022

-- Update
Upon further investigation, it might be a more broad issue, it looks like I am getting a similar error when running powershell scripts outside of my .csx scripts. Ugh... this should be fun.


Hey there,
I updated dotnet-script and my scripts are now giving me "Fatal error. Internal CLR error. (0x80131506)".

I am running Pop_OS 22.04. I don't recall having updated anything else around that time. My Omnisharp has "defaultTargetFramework": "net6.0". My syslog isn't showing anything while this is happening. I restarted just in case but the same thing is happening.

Is there anything relatively obvious that might have changed recently that I might have to account for that I might have missed when updating that I need to change in my omnisharp config or similar? Just trying to determine if the issue is actually dotnet-script in the first place.

I have another script that does my dotnet tools updates and it's output is quite basic. I should probably start keeping track of the version numbers when updates occur to see what might have updated.

Update script
#!/usr/bin/pwsh

foreach ($package in $(dotnet tool list --global | select-object -Skip 2)) {
    echo "dotnet tool update --global $($package.Split(" ", 2)[0])"
    dotnet tool update --global $($package.Split(" ", 2)[0])
}

Thanks,
-MH

@seesharper
Copy link
Collaborator

seesharper commented Sep 25, 2022

Thanks and please let us know if this is a problem outside of dotnet-script 👍 I don't really see how dotnet-script alone can cause such an error.

Possibly related dotnet/runtime#45557
and maybe https://stackoverflow.com/questions/61249001/what-is-the-meaning-of-the-runtime-error-internal-clr-error-0x80131506

More recent dotnet/runtime#69653

@MostHated
Copy link
Author

MostHated commented Sep 26, 2022

Another update -- While in the middle of writing an issue report to the PowerShell board, it simply stopped having an issue. My scripts are all working just fine now. I honestly have no idea.. Ok, though, I guess? lol.


Yeah, at first I had not seen the error outside of running a csx using dotnet-script, which is of course what made me think it was related off the bat, but that script is doing a number of things, such as calling powershell via new Process().

Doing some additional tests, I found the following when trying to call pwsh from bash:

zsh ❯ /bin/pwsh -c "ls"
Fatal error. Internal CLR error. (0x80131506)
[1]    2500627 IOT instruction (core dumped)  /bin/pwsh -c "ls"

~
zsh ✗  /usr/bin/pwsh -c "ls"
Fatal error. Internal CLR error. (0x80131506)
[1]    2505030 IOT instruction (core dumped)  /usr/bin/pwsh -c "ls"

I appreciate the links, I will do some looking around in there and see if anything helps. 👍
-MH

@seesharper
Copy link
Collaborator

Great 😃. Closing this for now 👍

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

2 participants