Don't call ICoreWindow::Activate

Don't call ICoreWindow::Activate

Apparently (?) unnecessary, and it sometimes hangs in that call.

This doesn't seem to help the 16s timeout (per tryjobs here), but
doesn't seem to hurt either, and I can run on a local VM this way
at least.

BUG=411147
Committed: https://crrev.com/ab2f6b9ce3ba02a2bf397a1f3b875171cc9abdc4
Cr-Commit-Position: refs/heads/master@{#295594}

[scottmg, 2014-09-18 00:39:44]

scottmg@chromium.org changed reviewers:
+ cpu@chromium.org

[ananta, 2014-09-18 00:52:47]

On 2014/09/18 00:39:55, scottmg wrote:

LGTM % no sideeffects :). Is there any catch here?

[Shrikant Kelkar, 2014-09-18 01:12:13]

On 2014/09/18 00:52:47, ananta wrote:
> On 2014/09/18 00:39:55, scottmg wrote:
> 
> LGTM % no sideeffects :). Is there any catch here?

LGTM!

There is one more window_->Activate() with big comment on top,
ChromeAppViewAsh::OnActivate(), you may want to try disabling that one too.

[scottmg, 2014-09-18 04:54:50]

On 2014/09/18 00:52:47, ananta wrote:
> On 2014/09/18 00:39:55, scottmg wrote:
> 
> LGTM % no sideeffects :). Is there any catch here?

Yeah, I have no idea. The tests all pass fine, and I used it locally and didn't
notice anything (switching back and forth between metro/desktop a few times).
But it definitely could affect something. Any suggestions on things I should
test?

[scottmg, 2014-09-18 17:13:08]

On 2014/09/18 01:12:13, Shrikant Kelkar wrote:
> On 2014/09/18 00:52:47, ananta wrote:
> > On 2014/09/18 00:39:55, scottmg wrote:
> > 
> > LGTM % no sideeffects :). Is there any catch here?
> 
> LGTM!
> 
> There is one more window_->Activate() with big comment on top,
> ChromeAppViewAsh::OnActivate(), you may want to try disabling that one too.

Tried removing that one (ps#2), but no improvement on the 16s thing. One tryjobs
is actually stuck and seems to be hanging, so I think I'll leave that one alone.
(I don't know if it was just by chance of course)

[scottmg, 2014-09-18 17:14:53]

On 2014/09/18 17:13:08, scottmg wrote:
> On 2014/09/18 01:12:13, Shrikant Kelkar wrote:
> > On 2014/09/18 00:52:47, ananta wrote:
> > > On 2014/09/18 00:39:55, scottmg wrote:
> > > 
> > > LGTM % no sideeffects :). Is there any catch here?
> > 
> > LGTM!
> > 
> > There is one more window_->Activate() with big comment on top,
> > ChromeAppViewAsh::OnActivate(), you may want to try disabling that one too.
> 
> Tried removing that one (ps#2), but no improvement on the 16s thing. One
tryjobs
> is actually stuck and seems to be hanging, so I think I'll leave that one
alone.
> (I don't know if it was just by chance of course)

deleting ps2, but log is
http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...
for reference.

[scottmg, 2014-09-18 17:15:13]

Patchset #2 (id:20001) has been deleted

[scottmg, 2014-09-18 21:53:26]

The CQ bit was checked by scottmg@chromium.org

[commit-bot: I haz the power, 2014-09-18 21:54:32]

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

[commit-bot: I haz the power, 2014-09-18 23:19:00]

Committed patchset #1 (id:1) as d8be3e6d5db978afedeef9160e7927b33dbab88f

[commit-bot: I haz the power, 2014-09-18 23:19:54]

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