Gstreamer Pipeline issue : PosixMemMap:84 mmap failed V2

[DaneLLL]

Hi,
This use-case is not supported. Dynamically linking/unlinking the sink may trigger memory leak. Would suggest use nvmultistreamtiler plugin.

For this use-case, a possible solution is to use udpsink. You can have 4 udp streams with individual port number. And dynamically destroy/launch the pipeline to switch between the streams:

udpsrc ! rtph265depay ! h265parse ! nvv4l2decoder ! nv3dsink sync=0

[EmilienR]

Hi,
Something that I don’t understand is that even without switching cameras ( taking out the function of switching ) so that only one camera is displayed during all the process, the problem appears. I don’t see where the memory leak appears if there is no switching.

[DaneLLL]

Hi,
For further clarification, you may remove the unlink/link in on_click_cam_1/2/3/4 and directly link to fakesink.

And since there’s no such issue while running gst-launch-1.0 command, you con compare with the command to debug the application code.

[EmilienR]

Hi,
Do you mean that having no sink for the other cameras can create a sort of memory leak that would not exist if they were linked to fakesink ? And so, when i’m switching camera, to link everytime the previous camera to fakesink

[DaneLLL]

Hi,
Linking each camera to fakesink is for testing purpose. To avoid switching between the cameras. Since dynamic unlinking/linking is not supported.

For a real use-case, would suggest link to udpsink. And you can construct the pipeline with udpsrc to decode the stream and display. And can switch to decode another stream.