Hi all,
Running into a reproducible crash in MCore (Warp v2.0.0dev39) and looking for advice.
Setup: 4x A10 GPUs, CUDA 12.8/12.4, PyTorch/LibTorch 2.12.1 (cuda12.9 build), RHEL/Rocky. ~23,000 particles, box 160.
Command:
MCore
--population m/22586_2_25_post_image_warp.population
--devicelist 1 2 3
--iter 0
Issue: Refinement completes fine, but it crashes during the "reconstructing and filtering" step with:
CUDA error: CUDA-capable device(s) is/are busy or unavailable
This then triggers a second, unhandled System.NotImplementedException in MCore.WorkerDied(), which crashes the whole program and hides the real root cause.
Troubleshooting so far:
- Ruled out a single bad GPU — reproduces across different nodes/GPU counts, even after excluding a GPU that threw an Xid 31 fault. I have tried on A10's and ls40's.
- GPU monitoring shows the "lead" GPU spiking to ~10GB+ memory while others idle during reconstruction — looks like all reconstruction work funnels onto one device, possibly exceeding VRAM or destabilizing its CUDA context.
- Tested with/without --cpu_memory — same crash either way.
- Confirmed torch/CUDA environment is sane and all GPUs are visible.
- Can't fully rule out host RAM pressure in one instance, but crash reproduces on other nodes regardless.
Has anyone hit this or have ideas on the underlying CUDA trigger or a workaround? Happy to share full stack traces, dmesg logs, or GPU/disk monitoring plots.
Full details/logs: https://github.com/warpem/warp/issues/495
Thanks!