DeepStream can't decode certain H265 streams properly

@mfoglio @bkh1

What I mean is that the gtreamer upgrade is causing the compatibility issues between h265parse and nvv4l2decoder on special streams. Because the video display using avdec_h265 is also corrupted as you attached before, there may be something special about this stream as well. Our hardware decoder don’t have as much fault-tolerant as some software decoders.

Please attach your whole pipeline and describe that in detail how long it takes to crash. You can also do some simple analyses yourself, like change the sink plugin to fakesink and run.

I have tried running the GST pipeline through CLI for about a week now and have not gotten a crash. We had the segmentation using the python APIs. We will follow up soon with a python example of what we have that should recreate the issue.

OK. If there’s a segmentation problem with the python demo, please open a new topic. If this topic discusses multiple issues at the same time, it may not be convenient for others to refer to. Thanks

Will do, we are still checking on that now. We will post to the appropriate topic once we are able to reliable reproduce

@yuweiw how can we get more details on the segmentation fault? Is there a way to save the log to a file?
The problem is that it takes about a day for the segmentation fault to happen. What is the best approach to have more logs?

Yes. You can save the log to a file, just add 2>&1|tee log.txt after your command. But segmetation issue may not be analyzed by log alone. You need to use the gdb tool to get the stack and also monitor your memory usage.
Again, about the new segmentation issue. Could you open a new topic? It is best to discuss only one related issue in a topic, which is more convenient for others to refer to.

Hi @fanzh, I wanted to follow up on this thread. The fix you provided above for DeepStream 6.4 was still causing segmentation fault on DeepStream 6.4.
However, it seems to work with DeepStream 7.0… We are however concerned that it could cause other issues with our production code given that it was designed for DeepStream 6.4.
Could you provide more info? Was the fix developed for DeepStream 7.0 by mistake or is it expected to work on DeepStream 7.0?
Thank you

Hi @mfoglio , we have discussed several related issues in this topic, like image crash issue, hang issue, segmentation issue. This makes it difficult for others to refer to. So could you open a new topic for the new issue? Thanks

This is still the same issue :)

I mean the image crash issue, hang issue, segmentation issue are different kinds of issues.

Now the latest issue is segmentation issue.

We will fix some of the previous bugs in the new version. Because there is not enough logs to analyze the cause of this segmetation problem, it is not possible to confirm whether it has been fixed on 7.0 version.
You can file a new topic only about the segmetation issue and provide sufficient information to analyze according to the method I attached before.