On Jetson TX2, I am launching a gstreamer pipeline with multiple plugins that load a serialized TensorRT engine from disk. This is done using gst-launch-1.0 and sometimes this works without any problem, but sometimes I get a segmentation fault. I vaguely remember reading somewhere that it’s a bad idea to concurrently load multiple TensorRT engines but can someone confirm this and perhaps point to where this is documented?
Also does anyone have an idea on a workaround for this using gst-launch-1.0?
Currently I put the initialization in the gst_infer_handle_sink_event function because that’s where I can read the frame width and height at runtime from a caps structure which I need to initialize some object that wraps the TensorRT execution context.
(In gstreamer there is also a gst_infer_init function but this also gets executed with gst-inspect-1.0 so I did not want to put this expensive operation of loading the TensorRT engine in there.)