tree 24b8f84461a1d95adc6666872b7545a3f8823d00
parent 9a4fd9bf740e799e1270604c8457202609a3d1e3
author Julien Isorce <julien.isorce@chromium.org> 1535746334 -0700
committer Commit Bot <commit-bot@chromium.org> 1535759369 +0000

ScreenCapturerMac: destroy the streams and remove the DisplayStreamManager

Thanks to the CL https://webrtc-review.googlesource.com/c/src/+/83822
there is now no need to destroy the stream asynchronously.
But the CL above introduced a leak, the streams were stopped but
not destroyed. This CL essentially fixes the leak, it is now safe
to destroy the stream right after being stopped as everything happen
in the same capture thread.

Bug: chromium:851883
Change-Id: I4bf7409246f3957d90040d0d8cf09e98f28d6559
Reviewed-on: https://webrtc-review.googlesource.com/96621
Reviewed-by: Brave Yao <braveyao@webrtc.org>
Reviewed-by: Zijie He <zijiehe@chromium.org>
Commit-Queue: Brave Yao <braveyao@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#24519}