we ran a dmesg command and found the following in the printout that may help
[ 15.569802] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.569817] Bluetooth: BNEP socket layer initialized
[ 16.067328] tegradc 15200000.nvdisplay: unblank
[ 16.067338] tegradc 15210000.nvdisplay: blank - powerdown
[ 16.067344] tegradc 15220000.nvdisplay: blank - powerdown
[ 25.626300] nvmap_alloc_handle: PID 9446: python3: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[ 36.190672] vdd-1v8-cvb: disabling
[ 36.190681] vdd-1v8-sd: disabling
[ 36.190686] vdd-epb-1v0: disabling
[ 36.190691] avdd-cam-2v8: disabling
[ 36.190696] vdd-sata-1v5: disabling
[ 36.190701] vdd-1v8-slt: disabling
[ 36.190705] vdd-3v3-slt: disabling
[ 36.190710] vdd_sys_en: disabling
[ 1014.729475] nvmap_alloc_handle: PID 23448: python3: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[ 1105.211844] nvmap_alloc_handle: PID 24301: python3: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[ 6026.806841] tegradc 15200000.nvdisplay: blank - p
cairo is a third party public library for 2D graphics.https://www.cairographics.org/
Deepstream use the cairo APIs to write text and draw graphics such as circle, rectangle, …
You may need to check the whether your app try to draw things out of boundary(such as draw bbox out of the video boundry).
I have tested and even if an objects label is too long, mianing it extends out of the bounds of the render window (not just its stream box) the program does not crash (usually it takes awhile for the program to crash)
The core dump means there is some operation happens without checking, so it is impossible to get the point by debug log. And the core dump happens in c code. You need to debug the core dump. There are lots of resources of core dump debugging in internet.
I really am struggling to determine the source of the issue.
So its possible that a python call could be causing the seg fault? (via the underlying C code of deepstream)
I have a crash log (from apport) which contains a core dump, once I have unpacked it the CoreDump is corrupted when i try and perform a back trace using gdb
the only real probe in my pipeline is on the tiler_sink_pad_probe, to read the metadata of objects and do some basic OSD changes like object labels, bounding box color.
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks