I am not sure the leaky queue works as expected in that scenario because I experienced the same issue. I opened a thread about that here: Gstreamer leaky queue stops the pipeline
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Deepstream pipeline memory leak | 5 | 214 | April 9, 2025 | |
| Decode MJPEG stream in deepstream use GPUs memory continuously increasing | 26 | 3229 | October 12, 2021 | |
| Memory leak when testing deepstream sample app | 42 | 1899 | April 20, 2023 | |
| Deepstream RTSP memory leak (with code to reproduce the issue) | 6 | 2561 | June 28, 2022 | |
| MJPEG rtsp source cause memory leak | 18 | 1542 | September 7, 2023 | |
| Memory Leak in Nvv4l2decoder | 3 | 848 | January 10, 2024 | |
| Nvv4l2decoder memory issue | 14 | 1117 | August 16, 2022 | |
| DeepStream 5.0 SDK Memory Leak | 18 | 2186 | October 12, 2021 | |
| Unexpected memory usage in deepstream-test3 | 25 | 2340 | July 6, 2021 | |
| Significant Memory leak when streaming from a clients RTSP source | 12 | 2795 | August 9, 2022 |