Skip to content

Conversation

@zasdfgbnm
Copy link
Collaborator

Fixes #29352

The newly added test fails consistently with illegal memory access without this PR, and now it succeeds consistently.

Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ngimel has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@mruberry mruberry changed the title Use handle pool to manage cuparse handles Use handle pool to manage cusparse handles Nov 9, 2019
zdevito pushed a commit to zdevito/ATen that referenced this pull request Nov 10, 2019
Summary:
Fixes pytorch/pytorch#29352

The newly added test fails consistently with illegal memory access without this PR, and now it succeeds consistently.
Pull Request resolved: pytorch/pytorch#29426

Differential Revision: D18407784

Pulled By: ngimel

fbshipit-source-id: 6cabb9a6674c25f7d7a3dc7b3bac99002018d8ee
@facebook-github-bot
Copy link
Contributor

@ngimel merged this pull request in 2032482.

@zasdfgbnm zasdfgbnm deleted the sparse-handle branch January 16, 2020 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cuSPARSE handle is not thread-safe

4 participants