Description
TiledCamera hangs indefinitely on RTX 5090 Laptop GPU (GB203), while the same code works perfectly on RTX 5090 Desktop GPU (GB202). Replacing TiledCameraCfg with CameraCfg resolves the issue on the Laptop GPU.
Environment Comparison
|
Laptop (HANGS) |
Server (WORKS) |
| GPU |
RTX 5090 Laptop (GB203, 24GB) |
RTX 5090 Desktop (GB202, 32GB) |
| Driver |
590.48.01 |
570.211.01 |
| CUDA |
13.1 |
12.8 |
| OS |
Ubuntu 22.04, Linux 6.8.0-101 |
Ubuntu 22.04 |
| Isaac Sim |
5.1.0 |
5.1.0 |
| Isaac Lab |
2.3.1 |
2.3.1 |
| Warp |
1.11.1 |
1.11.1 |
Symptoms
On the Laptop GPU (GB203):
- Process hangs at 100% CPU with no output or progress
- RSS/GPU memory remains constant
wchan=0 (CPU busy loop, not I/O wait)
- Hangs for 10+ minutes with no recovery
Investigation Results
- Warp kernel compilation works fine — standalone
reshape_tiled_image kernel compiles and executes successfully (258ms compile + run)
- Warp correctly detects sm_120 —
"cuda:0": "NVIDIA GeForce RTX 5090 Laptop GPU" (sm_120, mempool enabled)
- sm_120.ptx files exist — precompiled binaries are present
- The hang occurs in the tiled rendering pipeline (
omni.replicator layer), not in the warp kernel itself
Steps to Reproduce
- Use any Isaac Lab environment with
TiledCameraCfg sensors on an RTX 5090 Laptop GPU (GB203)
- Run the simulation — it will hang during the first render call
Example config:
from isaaclab.sensors import TiledCameraCfg
top_camera: TiledCameraCfg = TiledCameraCfg(
prim_path="{ENV_REGEX_NS}/top_camera",
offset=TiledCameraCfg.OffsetCfg(pos=(0.0, -0.065, 0.84), rot=(0.5, 0.5, -0.5, -0.5)),
data_types=["rgb"],
spawn=sim_utils.PinholeCameraCfg(
focal_length=2.12, focus_distance=400.0,
horizontal_aperture=3.6096,
clipping_range=(0.01, 20.0),
),
width=640, height=480,
)
Workaround
Replacing TiledCameraCfg with CameraCfg resolves the hang:
from isaaclab.sensors import CameraCfg
# Change all TiledCameraCfg → CameraCfg
Note: Camera and TiledCamera produce different pixel distributions (Issue #493), so this workaround may affect policy training/evaluation consistency.
Key Observation
The same GPU model (RTX 5090) with different chips behaves differently:
- GB202 (Desktop): TiledCamera works ✅
- GB203 (Laptop): TiledCamera hangs ❌
This suggests the issue is specific to the GB203 Laptop variant, possibly related to differences in shader core configuration or the tiled rendering pipeline's interaction with the Laptop GPU's Vulkan/RTX renderer.
Related Issues
Description
TiledCamera hangs indefinitely on RTX 5090 Laptop GPU (GB203), while the same code works perfectly on RTX 5090 Desktop GPU (GB202). Replacing
TiledCameraCfgwithCameraCfgresolves the issue on the Laptop GPU.Environment Comparison
Symptoms
On the Laptop GPU (GB203):
wchan=0(CPU busy loop, not I/O wait)Investigation Results
reshape_tiled_imagekernel compiles and executes successfully (258ms compile + run)"cuda:0": "NVIDIA GeForce RTX 5090 Laptop GPU" (sm_120, mempool enabled)omni.replicatorlayer), not in the warp kernel itselfSteps to Reproduce
TiledCameraCfgsensors on an RTX 5090 Laptop GPU (GB203)Example config:
Workaround
Replacing
TiledCameraCfgwithCameraCfgresolves the hang:Note:
CameraandTiledCameraproduce different pixel distributions (Issue #493), so this workaround may affect policy training/evaluation consistency.Key Observation
The same GPU model (RTX 5090) with different chips behaves differently:
This suggests the issue is specific to the GB203 Laptop variant, possibly related to differences in shader core configuration or the tiled rendering pipeline's interaction with the Laptop GPU's Vulkan/RTX renderer.
Related Issues