-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Internal CLR error when stepping over an await statement #13590
Comments
Can you provide a repro? I see you're using something called "ILEngine". I don't know what this is, but if it is generating IL it seems a likely source of this bug. |
I have the same issue while using Elasticsearch.Net at ElasticSearchStore#L42. You can reproduce it by running the sample. dotnet info
Stack Trace
|
Had the same error when using WPF and a lot of async code. Here comes my stacktrace:
|
Hello @softwaretirol, @TheMinefighter would it be possible to provide a dump for this issue? Also what version of .net core does this repro on? Thx |
Tagging subscribers to this area: @tommcdon |
@xsoheilalizadeh @TheMinefighter Do you see this issue only while debugging, or are you seeing the failure when not under the debugger? |
@davidwrighton I experienced the error debugging with JB Rider, It seems not to be possible to reproduce this reliably, or at least not for me. |
@tommcdon Sounds like this is a diagnostics bug. Please let me know if I can help if you can put a debugger repro together. |
@xsoheilalizadeh I tried a few hundred iterations of the requests with stepping. I could not repro any Execution Engine exceptions. At first sight this looks like an AV in the DAC, but without some dump or full trace including native frames this is going to be very hard to address. In the sample I can also see that the SDK is fixed to 3.1.100, can you try a more recent runtime and confirm if the issue still repros? |
A very similar stacktrace happens to me, under Windows Containers with dotnet core.
I'm in the process of replicating it. |
|
@xljiulang was this while running under the debugger and stepping through your code? |
@hoyosjs |
I'll open a new issue then :) That's a separate issue. |
I've just encountered this same exact error, although under slightly different circumstances; my program was not at all complex. I created a fresh console application for .NET Core 3.1, set the platform to x64, and instantiated a 2-dimensional 1-by-1 float array with a collection initializer. Stepping in debug mode throws an exception when running that line of code. Simply attempting to access a multidimensional array throws an exception as well. If not stepping, no exception is thrown. The only stack-trace it gave me was a single line for Main(), as that was where I attempted to create the array. |
@bobbymonboy that's a different issue: #38777 |
Unable to repro the issue, closing this issue until we have an actionable dump or repro. |
|
Do you get this error only when a debugger is attached? |
I spoke to soon. Ignore the previous post. For some bizarre reason I am getting this error today, where the code I am running has been the same, mostly and working for a while now. Bizarre. I don't have the debugger attached, I am in (console) RELEASE mode running massive parallel async/await load consuming many chips. Running .net 5 rc2 and possibly forgetting to set This is all the debug info I could find: Console stack that was dumped this time:
clr dotnet-dump stack clr threads with exceptions on them
|
Same here, when using google search api when waiting for the results. First time request goes ok, second time, crash badly. |
|
@egbertn was this only happening with the debugger attached? Also, do you have any version information? |
Yes, during debugging. |
Issue Title
During debugging an application, the app is crashing. It happens completly randomly, but most of the time if you step over an "await .." statement.
How can i provide you more information? It is a large .NET Core 3.0 application, so a sample is a little bit hard to create.
General
The text was updated successfully, but these errors were encountered: