HI
about your second issue, “a random “Segmentation Fault” or “double free or corruption (fasttop)”. It doesn’t happen regularly, can happen after 3 seconds or 5 minutes”
I can not repro your issue given by your steps from comment 13 within 10 mins.
Hi,
I find that very weird, that you couldn’t reproduce the things, I reported in comment 13 and 18.
Today I flashed a new Jetson with JetPack 4.2.2 to be sure (deepstream 4.0.1), I didn’t mess up anything on my old Jetson setup during development.
I followed the steps from comment 13, I had the same publishing problems as well as the segmentation fault error.
So my question is, were you actually able to reproduce the expected behavior? While following comment 13, I realized, that the msg-conv-comp-id was missing.
So here the updated config, in case you didn’t find that out yourself.
[application]
enable-perf-measurement=1
perf-measurement-interval-sec=5
[source0]
enable=1
type=3
uri=file:///opt/nvidia/deepstream/deepstream-4.0/samples/streams/sample_1080p_h264.mp4
num-sources=5
gpu-id=0
nvbuf-memory-type=0
[sink1]
enable=1
type=6
msg-conv-config=dstest5_msgconv_sample_config.txt
msg-conv-payload-type=0
msg-broker-proto-lib=/opt/nvidia/deepstream/deepstream-4.0/lib/libnvds_amqp_proto.so
#Provide your msg-broker-conn-str here
msg-broker-conn-str=rabbitmq;5672;guest
topic=detections2
msg-broker-config=cfg_amqp.txt
msg-conv-msg2p-lib=/opt/nvidia/deepstream/deepstream-4.0/lib/libnvds_msgconv.so
sync=0
msg-broker-comp-id=1
msg-conv-comp-id=1
[sink2]
enable=1
type=6
msg-conv-config=dstest5_msgconv_sample_config.txt
msg-conv-payload-type=0
msg-broker-proto-lib=/opt/nvidia/deepstream/deepstream-4.0/lib/libnvds_amqp_proto.so
#Provide your msg-broker-conn-str here
msg-broker-conn-str=rabbitmq;5672;guest
msg-broker-config=cfg_amqp.txt
topic=detections
msg-conv-msg2p-lib=/opt/nvidia/deepstream/deepstream-4.0/lib/libnvds_msgconv.so
sync=0
msg-broker-comp-id=2
msg-conv-comp-id=2
[osd]
enable=1
gpu-id=0
border-width=1
text-size=15
text-color=1;1;1;1;
text-bg-color=0.3;0.3;0.3;1
font=Arial
show-clock=0
clock-x-offset=800
clock-y-offset=820
clock-text-size=12
clock-color=1;0;0;0
nvbuf-memory-type=0
[streammux]
gpu-id=0
live-source=1
batch-size=5
batched-push-timeout=40000
width=608
height=608
enable-padding=0
nvbuf-memory-type=0
[primary-gie]
enable=1
gpu-id=0
batch-size=5
bbox-border-color0=1;0;0;1
bbox-border-color1=0;1;1;1
bbox-border-color2=0;1;1;1
bbox-border-color3=0;1;0;1
nvbuf-memory-type=0
interval=0
gie-unique-id=1
config-file=config_infer_primary_nano.txt
model-engine-file=../../models/Primary_Detector/resnet10.caffemodel_b5_fp16.engine
[tests]
file-loop=1
Our internal team was able to reproduce the message duplication/corruption and segfault using DS 4.0.2. The fix will be in an upcoming release. The fix is our AMQP adapter library which is currently not released in source form, so we cannot easily share it at the moment.