Skip to content

Fix error checking of CUDA multi_margin_loss. #30825

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

Closed
wants to merge 1 commit into from

Conversation

gchanan
Copy link
Contributor

@gchanan gchanan commented Dec 5, 2019

Stack from ghstack:

It didn't verify in the 1-d case that the targets were size 1..

Differential Revision: D18833659

It didn't verify in the 1-d case that the targets were size 1..

[ghstack-poisoned]
@albanD
Copy link
Collaborator

albanD commented Dec 5, 2019

Does that leak memory on error as well?

@gchanan
Copy link
Contributor Author

gchanan commented Dec 5, 2019

looks like it, but the test doesn't catch it because all the combinations are valid (unlike MultiLabelMargin where they aren't, so they trigger the errors).

@facebook-github-bot
Copy link
Contributor

@gchanan merged this pull request in 0974dcc.

@facebook-github-bot facebook-github-bot deleted the gh/gchanan/165/head branch December 10, 2019 15:19
wuhuikx pushed a commit to wuhuikx/pytorch that referenced this pull request Jan 30, 2020
Summary:
Pull Request resolved: pytorch#30825

It didn't verify in the 1-d case that the targets were size 1..

Test Plan: Imported from OSS

Differential Revision: D18833659

Pulled By: gchanan

fbshipit-source-id: 9b0276e7b0423fdaf2ba7cfa34bde541558c61f9
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.

4 participants