Memory Leak due to RTCP about scream

[remmius]

Pipeline to reproduce the issue on localhost with 1 computer.
Sender:

• gst-launch-1.0 rtpbin name=rtpbin ! videotestsrc is-live=true ! timeoverlay ! video/x-raw,width=640,height=480, framerate=30/1 ! videoconvert ! x264enc name=video tune=zerolatency ! rtph264pay ! 'application/x-rtp, payload=(int)96' ! gscreamtx media-src=0 ! rtpbin.send_rtp_sink_0 rtpbin.send_rtp_src_0 ! udpsink host=127.0.0.1 port=7878 rtpbin.send_rtcp_src_0 ! 'application/x-rtcp' ! tcpclientsink host=127.0.0.1 port=5002 tcpclientsrc host=127.0.0.1 port=5002 ! 'application/x-rtcp' ! rtpbin.recv_rtcp_sink_0
  Receiver:
• gst-launch-1.0 rtpbin name=rtpbin ! udpsrc port=7878 ! 'application/x-rtp, encoding-name=(string)H264, payload=(int)96' ! gscreamrx ! application/x-rtp,media=video,clock-rate=90000,encoding-name=H264 ! rtpbin.send_rtp_sink_0 rtpbin. ! rtph264depay ! queue ! avdec_h264 ! xvimagesink sync=false tcpserversrc port=5002 ! 'application/x-rtcp' ! rtpbin.recv_rtcp_sink_0 rtpbin.send_rtcp_src_0 ! 'application/x-rtcp' ! tcpserversink port=5002 host=127.0.0.1 sync=false async=false

As the rtcp-feedback is done via a tcp-connection, it is necessary to start the receiver side before the sender side. However, with a tcp-connection it was much easier to make it running regarding the ports/nat...