-
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
memcpy/memset helpers on CoreCLR may not be suspension-friendly #98620
Comments
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Feb 17, 2024
VSadov
added
area-VM-coreclr
and removed
untriaged
New issue has not been triaged by the area owner
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
labels
Feb 17, 2024
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Feb 17, 2024
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Feb 25, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This came in discussions for another fix:
#98547 (comment)
We generally try avoiding unbounded operations that may happen in coop mode while running native code as they may result in arbitrary long pauses when nothing runs except the said operation.
(the operation starves GC and GC starves the rest of the app threads)
This scenario should be looked at and if needed either move to managed code, or make it happen piece-wise interleaved with suspension opportunities.
The text was updated successfully, but these errors were encountered: