You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I faced this issue while running pytorch application but some similar issues were mentioned for julia as well (referenced here: #JuliaLang/julia#49246)
RuntimeError: Error in dlopen: libtorch_cuda_linalg.so: cannot open shared object file: No such file or directory
The first hit was correct (trying file=home/abastol/modules/anaconda3/envs/newsn/bin/../lib/libtorch_cuda_linalg.so) but the not sure about the second one. There were two windows opened so not sure if the second hit (trying file=/usr/lib/libtorch_cuda_linalg.so)was for that (some concurrency issue perhaps).
Anyway a manual export to the conda env library path seems to fix this issue (referenced here:#JuliaLang/julia#49246) but this might be temporary.
The text was updated successfully, but these errors were encountered:
I believe this is a duplicate of #107. If so, it is a known issue, and the workaround is documented in the VirtualGL User's Guide. (The workaround is just a convenience option to vglrun that does exactly what you describe: adding the application's library directory to LD_LIBRARY_PATH. Refer to #107 and the VirtualGL User's Guide for an explanation of why that is necessary.)
I faced this issue while running pytorch application but some similar issues were mentioned for julia as well (referenced here: #JuliaLang/julia#49246)
RuntimeError: Error in dlopen: libtorch_cuda_linalg.so: cannot open shared object file: No such file or directory
Here is the debug output:
The first hit was correct (trying file=home/abastol/modules/anaconda3/envs/newsn/bin/../lib/libtorch_cuda_linalg.so) but the not sure about the second one. There were two windows opened so not sure if the second hit (trying file=/usr/lib/libtorch_cuda_linalg.so)was for that (some concurrency issue perhaps).
Anyway a manual export to the conda env library path seems to fix this issue (referenced here:#JuliaLang/julia#49246) but this might be temporary.
The text was updated successfully, but these errors were encountered: