After long time , the fps drop to zero

Accelerated Computing Intelligent Video Analytics DeepStream SDK
1 
 I use deep-stream 4.0.2 to run 3 rtsp camera, after run for 12 hours, the fps of

one rtsp camera drop to zero, then several hours the another camera drop to zero.
do you know why?

the follow is the log:
**PERF: FPS 0 (Avg) FPS 1 (Avg) FPS 2 (Avg)
**PERF: 10.06 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.01 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.97 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.02 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.94 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.02 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.01 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.02 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.01 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.94 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.06 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.10 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.93 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.98 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.91 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.05 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 9.94 (9.96) 0.00 (9.98) 0.00 (9.96)
**PERF: 10.01 (9.96) 0.00 (9.98) 0.00 (9.96)

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) Jetson Tx2
• DeepStream Version 4.0.2
• JetPack Version (valid for Jetson only) JetPack 4.3
• TensorRT Version TensorRT6
• NVIDIA GPU Driver Version (valid for GPU only)

3

Seems two of the streams stop. There is no information for us to know what happened. Can you try to check the tcp connection status and udp packet lost status?

4

I use ping to test the camera , the delay is less than 1ms, and use browser to open the camera, the display is ok.

5

Are you using deepstream-app? Can you update to Deepstream 5.0 DP version? We have added reconnection feature for RTSP.
Please add “rtsp-reconnect-interval-sec” to the source config in the config file with Deepstream 5.0 DP.

https://docs.nvidia.com/metropolis/deepstream/dev-guide/index.html#page/DeepStream_Development_Guide/deepstream_app_config.3.2.html#wwpID0E0XB0HA

6

sorry, jetpack4.3 can’t use deepstream 5.0 DP, and the problem happen in my real application, I can’t upgrade the jetpack.we must fix it in current environment . please help me how to check the problem and how to fix in deepstream 4.0.2 . thanks.

7

after long time， the deepstream report
“FMO streams not supported for T210 onwards”
and
“**PERF: FPS 0 (Avg) FPS 1 (Avg) FPS 2 (Avg)
**PERF: 10.61 (19.93) 20.04 (0.37) 0.00 (19.90)
ERROR from rtph264depay0: The stream is in the wrong format.
Debug info: gstrtph264depay.c(1270): gst_rtp_h264_depay_process (): /GstPipeline:pipeline/GstBin:multi_src_bin/GstBin:src_sub_bin0/GstURIDecodeBin:src_elem/GstDecodeBin:decodebin0/GstRtpH264Depay:rtph264depay0:
NAL unit type 26 not supported yet
Quitting
App run failed”

8

the log is "
**PERF: FPS 0 (Avg) FPS 1 (Avg) FPS 2 (Avg)
**PERF: 19.99 (19.93) 0.00 (19.94) 0.00 (19.90)
**PERF: 19.90 (19.93) 0.00 (19.94) 0.00 (19.90)
**PERF: 19.90 (19.93) 0.00 (19.94) 0.00 (19.90)
FMO streams not supported for T210 onwards
**PERF: 20.07 (19.93) 0.00 (0.34) 0.00 (19.90)
**PERF: 19.94 (19.93) 19.94 (0.34) 0.00 (19.90)
**PERF: 20.01 (19.93) 20.01 (0.34) 0.00 (19.90)
**PERF: 20.03 (19.93) 20.03 (0.34) 0.00 (19.90)
**PERF: 19.99 (19.93) 19.99 (0.34) 0.00 (19.90)
**PERF: 19.94 (19.93) 19.94 (0.35) 0.00 (19.90)
**PERF: 19.73 (19.93) 19.93 (0.35) 0.00 (19.90)
**PERF: 20.06 (19.93) 20.06 (0.35) 0.00 (19.90)
**PERF: 20.24 (19.93) 20.04 (0.35) 0.00 (19.90)
**PERF: 19.95 (19.93) 20.15 (0.35) 0.00 (19.90)
**PERF: 20.02 (19.93) 20.02 (0.35) 0.00 (19.90)
**PERF: 19.88 (19.93) 20.08 (0.36) 0.00 (19.90)
**PERF: 20.03 (19.93) 20.03 (0.36) 0.00 (19.90)
**PERF: 19.70 (19.93) 19.90 (0.36) 0.00 (19.90)
**PERF: 20.05 (19.93) 20.05 (0.36) 0.00 (19.90)
**PERF: 19.94 (19.93) 20.14 (0.36) 0.00 (19.90)
**PERF: 13.44 (19.93) 20.01 (0.36) 0.00 (19.90)

**PERF: FPS 0 (Avg) FPS 1 (Avg) FPS 2 (Avg)
**PERF: 10.61 (19.93) 20.04 (0.37) 0.00 (19.90)
ERROR from rtph264depay0: The stream is in the wrong format.
Debug info: gstrtph264depay.c(1270): gst_rtp_h264_depay_process (): /GstPipeline:pipeline/GstBin:multi_src_bin/GstBin:src_sub_bin0/GstURIDecodeBin:src_elem/GstDecodeBin:decodebin0/GstRtpH264Depay:rtph264depay0:
NAL unit type 26 not supported yet
Quitting
App run failed
"

9

@Mike_deng Unfortunately, there is no fix for the re-connection problem for Deepstream 4.0.2. You may check the relevant parts of Deepstream 5.0 codes and port it.

The log you gave above has told you there are some unsupported features in the h264 stream.

10

Hi Fiona,
thank for reply , as your suggestion, I merged the reconnect code to 4.0.2, most change in deepstream_source_bin.c, but after build deepstream-app ,it can’t enter the added function, I guess it need to update the lib file, do you know, after changed deepstream_source_bin.c, which so file need to update.

thanks

11

No library updated by deepstream_source_bin.c, just replace the bin is OK.

12

I update the deepstream-app, but it didn’t print the message which I add in create_rtsp_src_bin.

13

Have you modified deepstream_config_file_parser.c and deepstream_sources.h too?

14

yes， I do it. and it is ok to make

15

for to test , i only add printf in create_source_bin, then compile it. i didn’t see the printf information

16

the problem was resolved, the type need to set 4 in config file， it is 3 in my old config file.

18

today , I met a new problem.
(deepstream-app:14337): GLib-GObject-WARNING **: 14:06:44.170: g_object_set_is_valid_property: object class ‘nvv4l2decoder’ has no property named ‘rtsp-reconnect-interval-sec’

do you know the reason, if i need to update something.

19

Hi Mike_deng,

Please help to open a new topic for your issue. Thanks

20

I had create new topic.