-
Notifications
You must be signed in to change notification settings - Fork 863
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
System.AccessViolationException -- seems like yarp has some issues with memory #2374
Comments
This appears to be an issue with the built-in telemetry in .NET, not specific to YARP. Is the stack trace always the same? |
the stack trace is always the same, since this error happens in prod and is sporadic not sure how i can capture a mem dump on it |
You can collect a dump when crashing by setting an environment variable, see https://learn.microsoft.com/dotnet/core/diagnostics/collect-dumps-crash |
it doesn't seem to crash yarp, maybe kestral or whatever built in lib catches this error |
I believe that seeing |
Triage: Not actionable without a dump. Once you have a dump, feel free to reopen. Note: Given that the stack is suspicious, check that it happens on more than 1 machine. Chasing down 1 machine config/HW issues is very time consuming for everyone. |
You were hitting dotnet/runtime#99603. Please watch that issue for updates |
Describe the bug
This error pops up in production about 5 times a day, couldn't connect it to anything special, the pod doesn't go OOM, yarp doesn't report any special spikes in requests or latency, and no other errors in logs connected to this.
each yarp deployment is handling an avg. of 4 requests per second which shouldn't be too many i think
To Reproduce
Not sure
Got Exceptions? Include both the message and the stack trace
Further technical details
The text was updated successfully, but these errors were encountered: