We are still debugging this. It may be related to a TensorTRT minor version change, or something like that, impacting in the yolo.so lib file. So far we couldn’t find we comes from. Thanks.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Issue with Bounding Boxes and Object Detection in DeepStream Using YOLOv8 Model | 9 | 130 | April 18, 2025 | |
| Deepstream Sample app deepstream-test3 memory leak | 2 | 393 | November 27, 2023 | |
| DeepStream 6 Tracker removes PGIE outputs | 15 | 882 | July 28, 2022 | |
| How to solve the memory leak in Deepstream Yolov8s-seg | 11 | 74 | April 29, 2025 | |
| How to use custom object detector i.e nvinfer in ds-example | 6 | 2386 | October 12, 2021 | |
| Input Tensor is unexpectedly modified before fetched to primary detector | 8 | 448 | March 8, 2024 | |
| TensorRT engine giving wrong/different output in DeepStream | 26 | 4178 | February 22, 2022 | |
| Error in output of yolov5 models when using triton + deepstream integration | 12 | 847 | August 8, 2023 | |
| Yolov5 giving unexpected outputs | 5 | 1836 | October 12, 2021 | |
| When I finished deploying YoloV5, it worked poorly, detecting a video that yielded very few targets and all of them were wrong | 5 | 533 | September 8, 2022 |