Fixing perf regression caused by refactoring full stack tests

Fixing perf regression caused by refactoring full stack tests

Calling CreateCapturer after CreateStreams. The wrong order of calling those methods seems to have caused perf regressions.

Testing has been done here: https://codereview.webrtc.org/1371113004/

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

[ivica, 2015-10-07 09:57:30]

The CQ bit was checked by ivica@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2015-10-07 09:57:35]

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

[ivica, 2015-10-07 10:01:05]

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

[commit-bot: I haz the power, 2015-10-07 11:05:31]

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

[commit-bot: I haz the power, 2015-10-07 11:05:32]

Dry run: This issue passed the CQ dry run.

[sprang_webrtc, 2015-10-08 09:39:28]

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

[sprang_webrtc, 2015-10-08 09:39:28]

rs lgtm
+pbos@, ptal. Any idea why this would change the behavior?

[pbos-webrtc, 2015-10-08 09:47:50]

Looking at it the timer is started in FrameGeneratorCapturer::Init() so this is
slightly different timing wise.

lgtm, bah

[ivica, 2015-10-08 09:58:52]

The CQ bit was checked by ivica@webrtc.org

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

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

[commit-bot: I haz the power, 2015-10-08 10:44:12]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-08 10:44:20]

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