GitLab

It was noticed that incoming packets are now handled on the WebRTC
signaling thread. This is problematic because many JS WebRTC API calls
get indirectly executed there due to WebRTC's synchronous proxies. And
vice versa - lots of packet handling can delay API calls.

This change adds an enabled-by-default feature called
WebRtcDistinctWorkerThread which splices out WebRTC's worker execution
into its own thread - decoupling the packet processing from the signal
thread.

Bug: 1157617
Change-Id: I16998a3ae0df022ffd544f5a3e2d7d8ada1acfb3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546006
Commit-Queue: Markus Handell <handellm@google.com>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#835887}