NVIDIA DeepStream 9.1 bug causes RTSP process aborts during reconnection
Developers have identified a reproducible bug in the NVIDIA DeepStream 9.1 SDK where the nvurisrcbin component causes a process abort during RTSP reconnection when NTP synchronization is active. Users have successfully mitigated the issue by replacing the component with uridecodebin, which maintains stability and accurate timing without causing crashes.
Key Takeaways
- The nvurisrcbin component in DeepStream 9.1 causes unrecoverable process aborts during forced RTSP reconnections when using NTP/RTCP sync.
- Replacing nvurisrcbin with uridecodebin resolved the issue in testing, maintaining stability across 50 consecutive reconnections without core dumps.
- NTP timestamp accuracy remains high with the workaround, showing a median error of approximately 6 ms compared to MediaMTX recordings.
- The failure bypasses standard Python try/except blocks, appearing as a low-level signal abort (SIGABRT) that necessitates a full process restart.
Why It Matters
For streaming infrastructure reliant on the NVIDIA Metropolis stack, this bug represents a significant reliability gap in automated monitoring and retail analytics. Immediate implications include the risk of total system failure during minor network blips if using the native nvurisrcbin for synchronized multi-camera feeds. Within the broader ecosystem, this highlights a recurring friction point in GStreamer-based SDKs: the trade-off between NVIDIA’s optimized helper bins and the stability of upstream GStreamer elements. Engineers should track upcoming DeepStream 9.1 patch notes for a fix to internal rtspsrc state handling, as the current workaround requires more complex manual management of the source bin lifecycle.
Additional Context
The DeepStream 9.1 SDK was released in July 2026, introducing significant architectural shifts, including a transition to an open-source monorepo on GitHub and support for the JetPack 7.2 platform on NVIDIA Orin and Thor hardware. Per NVIDIA’s release documentation from July 2026, the update was centered on "agentic AI" capabilities, allowing developers to build complex multi-camera pipelines using natural language prompts rather than manual GStreamer wiring. This release also prioritized Multi-View 3D Tracking (MV3DT) and AutoMagicCalib, features designed to synchronize object IDs across disparate camera views in a shared 3D coordinate system.
Despite these advancements, RTSP stability has been a persistent challenge for the SDK. Reports from the NVIDIA Developer Forums in July 2026 indicated similar reconnection "freezes" in DeepStream 8.0 on Jetson Thor platforms, where internal cleanup steps for dead sockets would hang indefinitely. Furthermore, GStreamer 1.24.2, which serves as the foundation for this DeepStream version, was released as a stable bug-fix update in April 2024 (per GStreamer.org), yet low-level interactions between NVIDIA’s proprietary bin wrappers and GStreamer's rtspsrc continue to surface in multi-stream production environments. These stability issues often force enterprise users to revert to standard GStreamer elements like uridecodebin to ensure the 99.9% uptime required for industrial and security deployments.
Read full article at forums.developer.nvidia.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source