-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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.OutOfMemoryException: at System.Buffers.TlsOverPerCoreLockedStacksArrayPool`1.Rent #9737
Comments
@benaadams Is your comment on dotnet/corefx#27185 implying you have a way to consistently reproduce this? |
No, a way to not use the
More specifically outlined in the use case of this api request https://github.com/dotnet/corefx/issues/27268 The Related issue of the ArrayPool consuming available memory https://github.com/dotnet/corefx/issues/25841 |
Ok thanks for the clarification. |
@jkotas Does this appear actionable? If so, could you help triage it? If not, please close. |
Related to or duplicate of https://github.com/dotnet/corefx/issues/25841 and https://github.com/dotnet/coreclr/issues/7747 . |
yes, all these should be dups of https://github.com/dotnet/corefx/issues/25841. GC just provides an API to indicate what memory situation we are in; it's really up to the pool implementation to decide on trimming. |
Unfortunately I was unable to get a dump of the process before the app service was restarted, but we have never encountered this before. No rhyme or reason - there was no memory pressure on the servers (web app - s3). I have attached the stack trace - though i don't think it will provide much.
Though the bigger question is, if this happens again, what should I trace or collect such that we have enough info.
thanks,
stephen
outofmemstacktrace.txt
The text was updated successfully, but these errors were encountered: