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
Describe the bug
GOMC dev code build on 11-27-21 yeilds random (does not happen all the time) segfaults when starting a job when multiple jobs on a GPU are running. Not 100% sure if this is a GOMC or GPU issue.
To Reproduce
Run the code I provide in the GOMC issues slack, as the code here is confidential. You will need manual access to a GPU so it can be potentially double -loaded. I personally loaded/ran them one after each other triple-loading the GPU.
Expected behavior
I would expect the code not to seg fault if a GPU is loaded with more than 1 GOMC simulation
Screenshots
No real info except "Segmentation fault (core dumped)"
Input files
Run the code I provide in the GOMC issues slack, as the code here is confidential.
Please complete the following information:
OS: RHEL 8.4
Ensemble: GEMC-NPT
Code version : GOMC dev code built with the code from 11-27-2021
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
GOMC dev code build on 11-27-21 yeilds random (does not happen all the time) segfaults when starting a job when multiple jobs on a GPU are running. Not 100% sure if this is a GOMC or GPU issue.
To Reproduce
Run the code I provide in the GOMC issues slack, as the code here is confidential. You will need manual access to a GPU so it can be potentially double -loaded. I personally loaded/ran them one after each other triple-loading the GPU.
Expected behavior
I would expect the code not to seg fault if a GPU is loaded with more than 1 GOMC simulation
Screenshots
No real info except "Segmentation fault (core dumped)"
Input files
Run the code I provide in the GOMC issues slack, as the code here is confidential.
Please complete the following information:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: