Hi,
We’re running 4x ZED X stereo cameras (8 GMSL2 streams) on a Jetson AGX Orin 64GB and experiencing nvargus-daemon crashes after 20-45 minutes of continuous streaming. Looking for any
known workarounds or ZED SDK-level mitigations.
Setup
- Jetson AGX Orin 64GB Developer Kit
- 4x ZED X cameras connected via GMSL2 capture board
- L4T 36.4.4 (JetPack 6.2.1)
- ZED SDK 5.x
- All 4 cameras opened simultaneously, streaming 1080p30
enableCamInfiniteTimeout=1set in nvargus-daemon service
Problem
After 20-45 minutes of continuous streaming, all cameras fail simultaneously. Two failure modes:
- nvargus-daemon SEGV — daemon crashes with FUSA VI handler
InvalidState/Corr Errorin journal, then restarts. Allsl::Camera::grab()calls return FAILURE permanently
after this. - Camera FAILURE without daemon crash — ZED SDK reports
FAILURE in sl::Camera::grab()andCAMERA REBOOTINGon all cameras at once. nvargus-daemon stays running but cameras
never recover.
In both cases, the only recovery is restarting nvargus-daemon + reopening all ZED camera sessions.
What works
- Short recordings (10s-15min) with stop/start cycles: 100% reliable across 40+ tests
- The failure only occurs with sustained continuous streaming beyond ~20 min
- Restarting nvargus-daemon between recording batches prevents the issue entirely
What we’ve tried
enableCamInfiniteTimeout=1— already enabled, doesn’t prevent the crash- Checked kernel modules — our
host1x-fence.koandcapture-ivc.koappear to be missing patches that NVIDIA has distributed on the forums for long-run multi-camera stability
(host1x-fence leak fix, capture-ivc semaphore
fix) - Filed a post on the NVIDIA Jetson forum requesting patched libraries/modules for L4T 36.4.4
Related threads
We’ve seen similar reports from other ZED X users — this doesn’t appear to be specific to our setup:
- ZED X stream crashing with multiple cameras — 3 cameras on AGX Orin, crashes after 20+ min,
unresolved - Unstable connection on AGX Orin 64G & JetPack 6.1 — Argus
timeouts, one user reports regression from SDK 4.2.2 → 5.1 - nvargus crashes intermittently with ZED X — Orin Nano, crashes
every 20min-4hrs - Camera hardware failure requires unplug — 4 cameras,
Failed to recover image capture... Timeoutafter hours - Restart zed_x_daemon doesn’t recover
cameras — AGX Orin, daemon restart
insufficient for recovery
Questions
- Is this a known issue with ZED X on AGX Orin with 4 cameras? Has Stereolabs been able to reproduce or characterize this internally?
- Does the ZED SDK have any built-in mechanism to recover from
grab()FAILURE without closing and reopening all cameras? (e.g.,sl::Camera::reboot()or similar) - Is there a recommended maximum continuous streaming duration for multi-camera ZED X setups on Orin?
- Would upgrading or downgrading the ZED SDK help? One user in the threads above reported stability on SDK 4.2.2 / JetPack 6.0 that regressed on SDK 5.1 / JetPack 6.1.
- Any known interaction between ZED X driver version (
zed_x_daemon) and nvargus stability? Should we update or pin a specific version?
Any guidance appreciated. Happy to provide ZED_Diagnostic -c output or journal logs if helpful.
Thank you!