Revert of Preliminary change for new rtc rendering algorithm

Revert of Preliminary change for new rtc rendering algorithm (patchset #15 id:400001 of https://codereview.chromium.org/1265433003/ )

Reason for revert:
Blink layout test failures: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=media%2Fvideo-capture*

Original issue's description:
> Preliminary change for new rtc rendering algorithm:
>
> 1. Add trace flags for smoothness testing
>
> 2. Propagate render_time calculated in Jitter Buffer to media::VideoFrame for new rendering algorithm to use.
>
> 3. Move invalidation trigger to compositor thread.
>
> BUG=514873
>
> Committed: https://crrev.com/dde7ac68de3071061c47a1986a3344da0ffe1f7d
> Cr-Commit-Position: refs/heads/master@{#344572}

TBR=dalecurtis@chromium.org,mcasas@chromium.org,miu@chromium.org,sunnyps@chromium.org,piman@chromium.org,qiangchen@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=514873
Committed: https://crrev.com/12f28e6acb22e283dfa0d046c4df1463de0779f0
Cr-Commit-Position: refs/heads/master@{#344590}

[pfeldman, 2015-08-20 21:48:08]

Created Revert of Preliminary change for new rtc rendering algorithm

[commit-bot: I haz the power, 2015-08-20 21:50:59]

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

[commit-bot: I haz the power, 2015-08-20 21:53:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-08-20 21:54:23]

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

[qiangchen, 2015-08-20 23:55:51]

On 2015/08/20 21:54:23, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/12f28e6acb22e283dfa0d046c4df1463de0779f0
> Cr-Commit-Position: refs/heads/master@{#344590}

Is there a trybot that I can do the test?

From one stacktrace in your failure link, I doubt the cause could be that I did
not consider the case when there isn't a Compositor thread for Video Playing.
But I need to make it for sure before recommitting.

[pfeldman, 2015-08-21 00:02:48]

On 2015/08/20 23:55:51, qiangchenC wrote:
> On 2015/08/20 21:54:23, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/12f28e6acb22e283dfa0d046c4df1463de0779f0
> > Cr-Commit-Position: refs/heads/master@{#344590}
> 
> Is there a trybot that I can do the test?
> 
> From one stacktrace in your failure link, I doubt the cause could be that I
did
> not consider the case when there isn't a Compositor thread for Video Playing.
> But I need to make it for sure before recommitting.

Sure, it basically painted the whole webkit tree red. Running tests there should
do the trick.

[pfeldman, 2015-08-21 00:04:09]

http://build.chromium.org/p/chromium.webkit/waterfall?last_time=1440109648

[qiangchen, 2015-08-21 18:34:21]

On 2015/08/21 00:04:09, pfeldman wrote:
> http://build.chromium.org/p/chromium.webkit/waterfall?last_time=1440109648

Thanks. It looks my guess is correct. After handling no compositor thread case,
the code passes the webkit test.

Is there a way for me to go over the whole test procedure you ran on my CL? So
that I can make sure nothing is broken 
before committing my code again.
in_reply_to: 5639274879778816
send_mail: 1
subject: Revert of Preliminary change for new rtc rendering algorithm

[pfeldman, 2015-08-21 18:36:39]

On 2015/08/21 18:34:21, qiangchenC wrote:
> On 2015/08/21 00:04:09, pfeldman wrote:
> > http://build.chromium.org/p/chromium.webkit/waterfall?last_time=1440109648
> 
> Thanks. It looks my guess is correct. After handling no compositor thread
case,
> the code passes the webkit test.
> 
> Is there a way for me to go over the whole test procedure you ran on my CL? So
> that I can make sure nothing is broken 
> before committing my code again.
> in_reply_to: 5639274879778816
> send_mail: 1
> subject: Revert of Preliminary change for new rtc rendering algorithm

i'd ran it on a couple of bots that failed it and if it works, i would re-land.

[qiangchen, 2015-08-21 19:10:18]

On 2015/08/21 18:36:39, pfeldman wrote:
> On 2015/08/21 18:34:21, qiangchenC wrote:
> > On 2015/08/21 00:04:09, pfeldman wrote:
> > > http://build.chromium.org/p/chromium.webkit/waterfall?last_time=1440109648
> > 
> > Thanks. It looks my guess is correct. After handling no compositor thread
> case,
> > the code passes the webkit test.
> > 
> > Is there a way for me to go over the whole test procedure you ran on my CL?
So
> > that I can make sure nothing is broken 
> > before committing my code again.
> > in_reply_to: 5639274879778816
> > send_mail: 1
> > subject: Revert of Preliminary change for new rtc rendering algorithm
> 
> i'd ran it on a couple of bots that failed it and if it works, i would
re-land.

I've created https://codereview.chromium.org/1306203002 after rebase. Currently
running CQ dry run.