Hi, I tried to switch the pipleline using a same v42l camera as the stream input in deepstream-app. The basic idea is to parse different configuration A and B into two appCtx. In my working process, firstly I create A pipeline, and then pause A, destory A. Next I create B pipeline.
The problem is when I used the file as the source element, it seems like no problem. When I used the v42l source element. The program will crash during creating B pipeline. it seems like the nvinfer cause this problem. How could I fix this issue? Looking forward to your reply
[source0]
enable=0
type=3
#uri=file:///opt/nvidia/deepstream/deepstream-5.1/samples/streams/sample_1080p_h264.mp4
uri=file:///home/js/jc2.mp4 #if the type = 3, the num-source will indicate the number of URIs.
num-sources=1
#gpu-id=0
#cudadec-memtype=0
I tested the problem again and found it is not working for using file as stream input now. By the way, to avoid the name conflict, I used different source id but the same file for two different pipeline. Restarting A or restarting B pipeline has no problem. and pipeline B could also work using deepstream-app.
Can you write a simple reproducing app that we can run just with deepstream environment? If the problem is caused by deepstream, deepstream application is enough. We can not setup the whole environment as yours.
A pure deepstream thread will enter the main-loop and I need a main thread as a interrupt control, But I will try to recover this bug only use deepstream.
Hi, I have a reproducing app using only deepstream environment. The basic idea is when I am quitting the deepstream-app, restarting a new pipeline using the same configuration. And the program will be crashed with the same debugger tracing log. deepstream_app_main.cpp (28.9 KB)