# nvargus-daemon crash after 20-45 min with 4x ZED X (8 GMSL2 streams) on AGX Orin — L4T 36.4.4

**URL:** <https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839>\
**Category:** Software\
**Tags:** multi-camera, jetpack, jetson\
**Created:** [February 20, 2026, 9:59am UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839 "2026-02-20T09:59:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [February 20, 2026, 9:59am UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/1 "2026-02-20T09:59:53Z")

</div>

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=1` set in nvargus-daemon service

## Problem

After 20-45 minutes of continuous streaming, all cameras fail simultaneously. Two failure modes:

1. **nvargus-daemon SEGV** — daemon crashes with FUSA VI handler `InvalidState` / `Corr Error` in journal, then restarts. All `sl::Camera::grab()` calls return FAILURE permanently  
after this.
2. **Camera FAILURE without daemon crash** — ZED SDK reports `FAILURE in sl::Camera::grab()` and `CAMERA REBOOTING` on 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.ko` and `capture-ivc.ko` appear to be missing patches that NVIDIA has distributed on the forums for long-run multi-camera stability  
([host1x-fence leak fix](https://forums.developer.nvidia.com/t/kernel-memory-leak-per-frame-with-argus-cameras-r36-4/325399), [capture-ivc semaphore  
fix](https://forums.developer.nvidia.com/t/nvarguscamerasrc-crashes-after-a-few-hours-of-working/355130))
- Filed a post on the [NVIDIA Jetson forum](https://forums.developer.nvidia.com/) 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](https://community.stereolabs.com/t/zed-x-stream-crashing-with-multiple-cameras/9754) — 3 cameras on AGX Orin, crashes after 20+ min,  
unresolved
- [Unstable connection on AGX Orin 64G & JetPack 6.1](https://community.stereolabs.com/t/unstable-connection-problem-of-zed-x-on-jetson-agx-orin-64g-dk-jetpack6-1/10369) — Argus  
timeouts, one user reports regression from SDK 4.2.2 → 5.1
- [nvargus crashes intermittently with ZED X](https://community.stereolabs.com/t/nvargus-crashes-intermittently-with-jetson-orin-nano-and-zed-x-camera/4942) — Orin Nano, crashes  
every 20min-4hrs
- [Camera hardware failure requires unplug](https://community.stereolabs.com/t/camera-hardware-failure-during-streaming-requires-unplug/3590) — 4 cameras, `Failed to recover image capture... Timeout` after hours
- [Restart zed\_x\_daemon doesn’t recover  
cameras](https://community.stereolabs.com/t/restarting-zed-x-daemon-and-nvargus-daemon-service-doesnt-work-when-unplugging-and-replugging-the-cameras/8938) — AGX Orin, daemon restart  
insufficient for recovery

## Questions

1. Is this a known issue with ZED X on AGX Orin with 4 cameras? Has [Stereolabs](https://www.stereolabs.com/) been able to reproduce or characterize this internally?
2. 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)
3. Is there a recommended maximum continuous streaming duration for multi-camera ZED X setups on Orin?
4. 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.
5. 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!

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [February 20, 2026, 10:11am UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/2 "2026-02-20T10:11:17Z")

</div>

Hi @dieng-calder  
Welcome to the [Stereolabs](https://www.stereolabs.com/) community.

Thank you for the information that you provided, but the most important one is missing: the ZED X Driver version.

Please run the `sudo ZED_Diagnostic -c` command and share the JSON report file that it generates.  
It will provide all the relevant information I need to understand more about your system setup.

---

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [February 21, 2026, 9:31am UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/3 "2026-02-21T09:31:51Z")

</div>

> [@Myzhar](#):
>
> ZED\_Diagnostic

[ZED\_Diagnostic\_Results.json](https://community.stereolabs.com/uploads/short-url/ag9czIR2eL8vECYR9JnIlnclPrk.json) (62.6 KB)

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [February 23, 2026, 5:06pm UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/4 "2026-02-23T17:06:00Z")

</div>

```auto
"GMSL DRIVER": {
        "GMSL driver": "",
        "error": [
            "<b>No GMSL driver detected or not a Stereolabs board.</b>"
        ]
    },

```

the driver is not correctly installed.

I recommend you download the latest ZED X Driver v1.4.0 and install it:

> **[Discover optimized GMSL 2 drivers for your system. | Stereolabs](https://www.stereolabs.com/developers/drivers)**
>
> We offer native GMSL2 camera drivers for Stereolabs embedded computers and compatibility drivers for leading 3rd-party ECUs. Choose your platform to access the right drivers for your hardware setup.

---

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [February 28, 2026, 5:09am UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/5 "2026-02-28T05:09:53Z")

</div>

> [@Myzhar](#):
>
> `GMSL DRIVER`

see this newly generated json file, the previous file was generated in docker which doesn’t have /var/lib/dpkg/status mounted, check this newly generated file

[ZED\_Diagnostic\_Results.json](https://community.stereolabs.com/uploads/short-url/7IhCmr6K4dSQ5EsVFFPSWKQKxjl.json) (62.6 KB)

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [March 2, 2026, 12:55pm UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/6 "2026-03-02T12:55:22Z")

</div>

Hi @dieng-calder  
The report shows that the cameras are correctly detected and initialized.

I recommend you upgrade the driver to the latest v1.4.0, which brings stability improvements

---

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [March 19, 2026, 7:52pm UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/7 "2026-03-19T19:52:23Z")

</div>

Hi @Myzhar ,

We have updated to 1.4.0 but issue still exists, I think the fundamental issue is in the kernel in the nvargus layer which is fixed in latest L4T 36.4.4 so we need a new SDK + Zed Link driver that supports the newer version.

---

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [June 6, 2026, 12:29am UTC](https://community.stereolabs.com/t/nvargus-daemon-crash-after-20-45-min-with-4x-zed-x-8-gmsl2-streams-on-agx-orin-l4t-36-4-4/10839/8 "2026-06-06T00:29:46Z")

</div>

Confirming this is still happening on **JP 6.2.2 / L4T r36.5.0** with the latest ZED Link driver — 3× ZED X (6 GMSL2 streams) via the ZED SDK, `nvargus-daemon` SIGSEGV after ~8–13 min of continuous streaming. We traced it to the NVIDIA FUSA capture path (`fusaViHandler.cpp:869` syncpoint error → `Error 8` on all sensors → use-after-free crash in `libnvargus`), so it is below the SDK, in `nvargus`/`libnvscf`. Detailed core analysis + backtrace posted on the NVIDIA forum (threads 361085 and 366870) for visibility.

> **[Libnvscf.so CaptureScheduler deadlock persists on JP 6.2.2 / L4T r36.5.0 —...](https://forums.developer.nvidia.com/t/libnvscf-so-capturescheduler-deadlock-persists-on-jp-6-2-2-l4t-r36-5-0-gdb-backtrace-resource-timeline-attached/366870/18)**
>
> please also note this is worth information.
