Skip to content

isaac-sim:6.0.0 dev2 - Simulator freezes or fails to start when using Newton physics engine via WebRTC (headless mode) #621

@ShileiShan

Description

@ShileiShan

Description

Issue 正文 (Description)
📝 Overview
When using the latest WebRTC client to remotely connect to Isaac Sim 6.0.0 running on a server, it is currently impossible to use the Newton physics engine. The simulator either freezes completely or crashes upon startup, depending on the launch method. Switching back to PhysX works normally.

🔄 Steps to Reproduce & Behaviors
Scenario A: Freeze on runtime switch (via runheadless.sh)

Launch Isaac Sim using ./runheadless.sh.

Connect to the server via WebRTC client (PhysX backend works fine).

Switch the physics backend to Newton in the PhysicsScene.

Result: The entire simulator freezes immediately and stops responding.

Scenario B: Crash on startup (via isaac-sim.newton.sh)

Attempt to launch using ./isaac-sim.newton.sh while enabling WebRTC extensions and disabling the local UI window (headless).

For example, running with flags like --ext:omni.services.streamclient.webrtc --no-window.

Result: The simulator throws an error and fails to start completely.

🎯 Expected Behavior / Feature Request
Please fix the compatibility/deadlock issue between the Newton physics engine's Vulkan pipeline and WebRTC livestreaming in headless mode.

Please provide a dedicated startup script (e.g., runheadless.newton.sh) or official documentation on how to properly configure Newton with WebRTC in containerized/headless environments.

💻 Environment
Isaac Sim Version: 6.0.0

Deployment: Docker / Remote Server

Streaming Method: WebRTC Livestream

Isaac Sim version

6.0.0 dev2

Operating System (OS)

20.04

GPU Name

3080ti

GPU Driver and CUDA versions

Driver Version: 570.172.08 CUDA Version: 12.8

Logs

No response

Additional information

No response

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions