Using static frame generator when no scrolling

Using static frame generator when no scrolling

In screensharing full stack tests, instead of using YuvFileGenerator by default
when no scrolling is used, I always used ScrollingImageFileGenerator.
That possibly slowed down the test a little bit, at least for the slowed
devices, as it unnecessarily copied few MBs per frame.

BUG=chromium:534220
Committed: https://crrev.com/d4818e73042bc2402256977884c04d96084327fb
Cr-Commit-Position: refs/heads/master@{#10014}

[ivica, 2015-09-22 07:59:59]

ivica@webrtc.org changed reviewers:
+ pbos@webrtc.org

[pbos-webrtc, 2015-09-22 08:57:24]

lgtm

[ivica, 2015-09-22 08:59:02]

The CQ bit was checked by ivica@webrtc.org

[commit-bot: I haz the power, 2015-09-22 08:59:10]

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

[commit-bot: I haz the power, 2015-09-22 10:59:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-22 10:59:22]

Try jobs failed on following builders:
  android_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  android_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[ivica, 2015-09-22 12:46:13]

The CQ bit was checked by ivica@webrtc.org

[commit-bot: I haz the power, 2015-09-22 12:46:22]

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

[commit-bot: I haz the power, 2015-09-22 12:47:34]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-22 12:47:43]

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