CUDA 'sticky errors' and undefined behavior explained
blelbach · x · 2026-08-29
Explaining CUDA errors that bypass Python try-catch blocks (like illegal memory access), a developer clarified the terminology and mechanics:
- Sticky errors: The term for hard-to-contain failures.
- Cause: In modern architectures with unified memory, device-side undefined behavior can corrupt host-side state (e.g., the CUDA context), making them uncatchable at the Python layer.
More from Infra
- SK Hynix ties new US plant to looser chip equipment exports to China, sources say — pstAsiatech · 2026-10-15
- Perplexity's new embedding models: index with a 9B model, search with 0.6B — antoine_chaffin · 2026-10-15
- Unsloth ships GGUF quants for Nemotron 3.5: Bolt-74B runs in 24GB RAM — danielhanchen · 2026-10-15
- vLLM-Omni ships Day-0 serving for FLUX 3 Image Klein with BF16, FP8, NVFP4 support — vllm_project · 2026-10-15
- NVIDIA's Nemotron 3.5 Super VL lands training and inference support on Applied Compute — ypatil125 · 2026-10-15
- CoreWeave bond yield tops 16% as loans outlast customer contracts by ~2 years — tengyanAI · 2026-10-15