webrtcbin: Starting a video media stream some time after a session has been started results in....

...a long pause whereby a number of frames seem to be looped
repeatedly, after some time there will be a rapid "catchup event"
where lots of frames play very fast. During this whole time from
starting the video stream to normal playback some of the hosts CPU
cores are pegged at 100%. The longer the delay between starting the
session and starting the video stream the worse the situation, i.e.
the longer the time before video plays normally.

Does anybody have any idea why this is happening in terms of gstreamer
pipeline configuration? It feels to me like something is mixing up
epocs/timestamps between start of a session and start of the video
stream.

The video media stream at this point is from gstreamer to the browser.

Dan