Fix multi-threaded application fail when memory pool is enabled#606
Merged
okuta merged 6 commits intocupy:masterfrom Nov 2, 2017
Merged
Fix multi-threaded application fail when memory pool is enabled#606okuta merged 6 commits intocupy:masterfrom
okuta merged 6 commits intocupy:masterfrom
Conversation
a0a79de to
519c4dd
Compare
Member
|
LGTM! |
okuta
added a commit
to okuta/cupy
that referenced
this pull request
Nov 2, 2017
Fix multi-threaded application fail when memory pool is enabled
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.
This fixes #72.
I use
memGetInfo()Runtime API, which seems to be most harmless, to explicitly bind the context to the current thread.(I first tried
getDevice(), but seems that it does not create a context)