Skip to content
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

stuck on lock? #4

Closed
tyoc213 opened this issue May 31, 2020 · 1 comment
Closed

stuck on lock? #4

tyoc213 opened this issue May 31, 2020 · 1 comment

Comments

@tyoc213
Copy link

tyoc213 commented May 31, 2020

after almost all day and probably some hibernations...

I created an experiment just right after that tried to delete it...

image

I ended hiting once the stop button on top of the ipynb.

@stas00
Copy link
Owner

stas00 commented May 31, 2020

Thank you for your report, @tyoc213.

Yes, I see those occasionally. If you manage to create a reproducible test case please submit it and then it can be fixed.

Ideally I'd like to get rid of threads completely, as the current workaround is not only clunky, it's imprecise. I'm waiting for pytorch to implement support for multiple torch.cuda.max_memory_allocated() counters. When this happens threads will no longer be needed. So please vote on that issue and perhaps it'll be looked at.

@stas00 stas00 closed this as completed May 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants