fix GetThreadContext call failed in mono GC for unity 5.2.x#1294
Open
loadingcn wants to merge 1 commit intoUnity-Technologies:unity-5.2-stagingfrom
Open
fix GetThreadContext call failed in mono GC for unity 5.2.x#1294loadingcn wants to merge 1 commit intoUnity-Technologies:unity-5.2-stagingfrom
loadingcn wants to merge 1 commit intoUnity-Technologies:unity-5.2-stagingfrom
Conversation
Backport from commit: 3f39ea8e2e79c4d85db445aef97742eec4d56849 Previous comment: Calls to GetThreadContext may fail. Work around this by putting access in suspend/resume loop to advance thread past problematic areas where suspend fails. Capture context in per thread structure rather at suspend time rather than retreiving during push logic.
Collaborator
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport from commit: 3f39ea8e2e79c4d85db445aef97742eec4d56849
Previous comment:
Calls to GetThreadContext may fail. Work around
this by putting access in suspend/resume loop
to advance thread past problematic areas where
suspend fails. Capture context in per thread
structure rather at suspend time rather than
retreiving during push logic.