Revert of Split IncomingVideoStream into two implementations, with smoothing and without.

Revert of Split IncomingVideoStream into two implementations, with smoothing and without. (patchset #4 id:290001 of https://codereview.webrtc.org/2071473002/ )

Reason for revert:
Reverting again.  The perf regression does not seem to be related to dropping frames.

Original issue's description:
> Reland of Split IncomingVideoStream into two implementations, with smoothing and without.
>
> Original issue's description:
>
> Split IncomingVideoStream into two implementations, with smoothing and without.
>
> This CL fixes an issue with the non-smoothing implementation where frames were delivered on the decoder thread.  No-smoothing is now done in a separate class that uses a TaskQueue.  The implementation may drop frames if the renderer doesn't keep up and it doesn't block the decoder thread.
>
> Further work done:
>
> * I added TODOs and documentation for VideoReceiveStream::OnFrame, where we today grab 5 locks.
>
> * I removed the Start/Stop methods from the IncomingVideoStream implementations.  Now, when an instance is created, it should be considered to be "running" and when it is deleted, it's "not running".  This saves on resources and also reduces the amount of locking required and I could remove one critical section altogether.
>
> * I changed the VideoStreamDecoder class to not depend on IncomingVideoStream but rather use the generic rtc::VideoSinkInterface<VideoFrame> interface.  This means that any implementation of that interface can be used and the decoder can be made to  just use the 'renderer' from the config.  Once we do that, we can decouple the IncomingVideoStream implementations from the decoder and VideoReceiveStream implementations and leave it up to the application for how to do smoothing.  The app can choose to use the Incoming* classes or roll its own (which may be preferable since applications often have their own scheduling mechanisms).
>
> * The non-smoothing IncomingVideoStream implementation currently allows only 1 outstanding pending frame.  If we exceed that, the current frame won't be delivered to the renderer and instead we deliver the next one (since when this happens, the renderer is falling behind).
>
> * The lifetime of the VideoStreamDecoder instance is now bound to Start/Stop in VideoReceiveStream and not all of the lifetime of VideoReceiveStream.
>
> * Fixed VideoStreamDecoder to unregister callbacks in the dtor that were registered in the ctor. (this was open to a use-after-free regression)
>
> * Delay and callback pointers are now passed via the ctors to the IncomingVideoStream classes.  The thread primitives in the IncomingVideoStream classes are also constructed/destructed at the same time as the owning object, which allowed me to remove one more lock.
>
> * Removed code in the VideoStreamDecoder that could overwrite the VideoReceiveStream render delay with a fixed value of 10ms on construction.  This wasn't a problem with the previous implementation (it would be now though) but seemed to me like the wrong place to be setting that value.
>
> * Made the render delay value in VideoRenderFrames, const.
>
> BUG=chromium:620232
> TBR=mflodman
>
> Committed: https://crrev.com/e03f8787377bbc03a4e00184bb14b7561b108cbb
> Cr-Commit-Position: refs/heads/master@{#13175}

TBR=mflodman@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:620232
Committed: https://crrev.com/8e8222d0d249813b000cf4ee3ede1a6699c0d534
Cr-Commit-Position: refs/heads/master@{#13176}

[tommi, 2016-06-16 22:43:52]

The CQ bit was checked by tommi@webrtc.org

[tommi, 2016-06-16 22:43:52]

Created Revert of Split IncomingVideoStream into two implementations, with
smoothing and without.

[commit-bot: I haz the power, 2016-06-16 22:43:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2071093002/1

[commit-bot: I haz the power, 2016-06-16 22:44:08]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-16 22:44:17]

Description was changed from

==========
Revert of Split IncomingVideoStream into two implementations, with smoothing and
without. (patchset #4 id:290001 of https://codereview.webrtc.org/2071473002/ )

Reason for revert:
Reverting again.  The perf regression does not seem to be related to dropping
frames.

Original issue's description:
> Reland of Split IncomingVideoStream into two implementations, with smoothing
and without.
> 
> Original issue's description:
> 
> Split IncomingVideoStream into two implementations, with smoothing and
without.
> 
> This CL fixes an issue with the non-smoothing implementation where frames were
delivered on the decoder thread.  No-smoothing is now done in a separate class
that uses a TaskQueue.  The implementation may drop frames if the renderer
doesn't keep up and it doesn't block the decoder thread.
> 
> Further work done:
> 
> * I added TODOs and documentation for VideoReceiveStream::OnFrame, where we
today grab 5 locks.
> 
> * I removed the Start/Stop methods from the IncomingVideoStream
implementations.  Now, when an instance is created, it should be considered to
be "running" and when it is deleted, it's "not running".  This saves on
resources and also reduces the amount of locking required and I could remove one
critical section altogether.
> 
> * I changed the VideoStreamDecoder class to not depend on IncomingVideoStream
but rather use the generic rtc::VideoSinkInterface<VideoFrame> interface.  This
means that any implementation of that interface can be used and the decoder can
be made to  just use the 'renderer' from the config.  Once we do that, we can
decouple the IncomingVideoStream implementations from the decoder and
VideoReceiveStream implementations and leave it up to the application for how to
do smoothing.  The app can choose to use the Incoming* classes or roll its own
(which may be preferable since applications often have their own scheduling
mechanisms).
> 
> * The non-smoothing IncomingVideoStream implementation currently allows only 1
outstanding pending frame.  If we exceed that, the current frame won't be
delivered to the renderer and instead we deliver the next one (since when this
happens, the renderer is falling behind).
> 
> * The lifetime of the VideoStreamDecoder instance is now bound to Start/Stop
in VideoReceiveStream and not all of the lifetime of VideoReceiveStream.
> 
> * Fixed VideoStreamDecoder to unregister callbacks in the dtor that were
registered in the ctor. (this was open to a use-after-free regression)
> 
> * Delay and callback pointers are now passed via the ctors to the
IncomingVideoStream classes.  The thread primitives in the IncomingVideoStream
classes are also constructed/destructed at the same time as the owning object,
which allowed me to remove one more lock.
> 
> * Removed code in the VideoStreamDecoder that could overwrite the
VideoReceiveStream render delay with a fixed value of 10ms on construction. 
This wasn't a problem with the previous implementation (it would be now though)
but seemed to me like the wrong place to be setting that value.
> 
> * Made the render delay value in VideoRenderFrames, const.
> 
> BUG=chromium:620232
> TBR=mflodman
> 
> Committed: https://crrev.com/e03f8787377bbc03a4e00184bb14b7561b108cbb
> Cr-Commit-Position: refs/heads/master@{#13175}

TBR=mflodman@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:620232
==========

to

==========
Revert of Split IncomingVideoStream into two implementations, with smoothing and
without. (patchset #4 id:290001 of https://codereview.webrtc.org/2071473002/ )

Reason for revert:
Reverting again.  The perf regression does not seem to be related to dropping
frames.

Original issue's description:
> Reland of Split IncomingVideoStream into two implementations, with smoothing
and without.
>
> Original issue's description:
>
> Split IncomingVideoStream into two implementations, with smoothing and
without.
>
> This CL fixes an issue with the non-smoothing implementation where frames were
delivered on the decoder thread.  No-smoothing is now done in a separate class
that uses a TaskQueue.  The implementation may drop frames if the renderer
doesn't keep up and it doesn't block the decoder thread.
>
> Further work done:
>
> * I added TODOs and documentation for VideoReceiveStream::OnFrame, where we
today grab 5 locks.
>
> * I removed the Start/Stop methods from the IncomingVideoStream
implementations.  Now, when an instance is created, it should be considered to
be "running" and when it is deleted, it's "not running".  This saves on
resources and also reduces the amount of locking required and I could remove one
critical section altogether.
>
> * I changed the VideoStreamDecoder class to not depend on IncomingVideoStream
but rather use the generic rtc::VideoSinkInterface<VideoFrame> interface.  This
means that any implementation of that interface can be used and the decoder can
be made to  just use the 'renderer' from the config.  Once we do that, we can
decouple the IncomingVideoStream implementations from the decoder and
VideoReceiveStream implementations and leave it up to the application for how to
do smoothing.  The app can choose to use the Incoming* classes or roll its own
(which may be preferable since applications often have their own scheduling
mechanisms).
>
> * The non-smoothing IncomingVideoStream implementation currently allows only 1
outstanding pending frame.  If we exceed that, the current frame won't be
delivered to the renderer and instead we deliver the next one (since when this
happens, the renderer is falling behind).
>
> * The lifetime of the VideoStreamDecoder instance is now bound to Start/Stop
in VideoReceiveStream and not all of the lifetime of VideoReceiveStream.
>
> * Fixed VideoStreamDecoder to unregister callbacks in the dtor that were
registered in the ctor. (this was open to a use-after-free regression)
>
> * Delay and callback pointers are now passed via the ctors to the
IncomingVideoStream classes.  The thread primitives in the IncomingVideoStream
classes are also constructed/destructed at the same time as the owning object,
which allowed me to remove one more lock.
>
> * Removed code in the VideoStreamDecoder that could overwrite the
VideoReceiveStream render delay with a fixed value of 10ms on construction. 
This wasn't a problem with the previous implementation (it would be now though)
but seemed to me like the wrong place to be setting that value.
>
> * Made the render delay value in VideoRenderFrames, const.
>
> BUG=chromium:620232
> TBR=mflodman
>
> Committed: https://crrev.com/e03f8787377bbc03a4e00184bb14b7561b108cbb
> Cr-Commit-Position: refs/heads/master@{#13175}

TBR=mflodman@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:620232

Committed: https://crrev.com/8e8222d0d249813b000cf4ee3ede1a6699c0d534
Cr-Commit-Position: refs/heads/master@{#13176}
==========

[commit-bot: I haz the power, 2016-06-16 22:44:19]

Patchset 1 (id:??) landed as
https://crrev.com/8e8222d0d249813b000cf4ee3ede1a6699c0d534
Cr-Commit-Position: refs/heads/master@{#13176}

[tommi, 2016-06-17 08:00:05]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.webrtc.org/2078873002/ by tommi@webrtc.org.

The reason for reverting is: Relanding without the non-smoothing
implementation..