-
Notifications
You must be signed in to change notification settings - Fork 19
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
[BUG REPORT] "an illegal memory access was encountered" and "nanobind leak" #10
Comments
I tried to build from the source with all the My building command is |
There is also a leak issue reported by
|
Hi, Thanks for the report. I haven't tested Deleting the From what you described, it sounds like Line 124 in 485f82c
As a sanity check, if you can control the number of GPUs on which you run your code, could you try setting it to 1 and see if it works then? It would also be helpful to have a minimal reproducer (if possible) to try to reproduce the issue on my end. |
Resolving the multiple GPU case will require a few API changes to allow the user to explicitly specify a device. You would then be able to specify it for each thread in your parallel job. In the meantime, you should be able to work around this issue by masking out available devices on each thread via the import os
os.environ['CUDA_VISIBLE_DEVICES'] = device_id # Mark only the desired device as visible
# ... |
When I used
joblib.Parallel
withloky
backend to launch multiple jobs in parallel, the below error occurred:Also, the GPU memory allocation was strange: multiple processes allocated memory on GPU 0.
I tried to delete the corresponding code but it did not work 😢.
Would your mind give any suggestions? Thanks in advance!
The text was updated successfully, but these errors were encountered: