Repeated calls do not send Video/Audio

[S4Vi]

Hey, I was testing repeated calls within one application session and figured out that the camera/microphone do not get dropped safely. From this point on it is a little "random" if the next call will work with video and audio.

You have "GC.Collect()" in several parts of your code. Enabling the one I linked at the bottom does let the camera/microphone drop immediately and every next call does work fine. However this only works in Debug mode. As soon as this is built as "Master" for UWP, this call does cause a crash.

Could you provide some information about the "TO-DO" you placed there? I'm not really sure which references are meant to be cleared by the GC.Collect() call to enable repeated calls in one session. I would like to replace this by the safe calls.

GC.Collect() 1

[ritchielozada]

The wrapper is based on PeerCC and I experience the similar disconnect/reconnect issues on the setup with Unity but not on the XAML implementation using the UWP converted WebRTC library. The quick fix is to execute the GC.Collect() to clear the unused objects.

FWIW, I am working on switching the dependency to the original webrtc.org native libraries to support cross-platform and avoid these control issues. The amount of effort to implement this native code gives more utility than trying to get the UWP only setup to work. Unfortunately this doesn't help your current known issue.

[S4Vi]

I'm just curious about if I have some wrong timings or added something destructive to the code, but did you experience crashes with the GC.Collect() call? You seem to see it as a okay fix (what it may be), but in my case there are really crashes due of it.

The direction you are going with this sounds like the right one. I wish you good luck on this! Is it foreseeable to a certain degree on how long this next iteration will take to be finished?

[ritchielozada]

I can't recall the specific details on my crash conditions, but the last item I had to fix was with memory pinning to ensure the memory references are not moved -- which leads to a crash. Getting a crash with GC.Collect() -- most likely is due to a NET/Mono runtime object being garbage collected but the plugin/interop still assumes availability.

I don't have a definite schedule for switching this sample to use the webrtc.org libs, I'm working right now on doing hardware encode/decode (nvenc/nvdec) as the video streaming solution.