Fix crash introduced in https://codereview.chromium.org/179123002/

Fix crash introduced in https://codereview.chromium.org/179123002/

We could have a dangling pointer if the RenderProcessHost is destroyed
prior to the renderer going away while we have a suspended timer. This
can happen in the case of an intent triggered from an external app since
it reuses one tab, destroying the tab that was previously created by
that app. This happens early during resume, before webkit timers are
resumed.

BUG=352213
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=258544

[Yaron, 2014-03-20 17:41:49]

bump

[Yaron, 2014-03-20 22:14:28]

feng: can you take a look?

[Feng Qian, 2014-03-21 00:20:49]

lgtm

[Yaron, 2014-03-21 00:25:53]

The CQ bit was checked by yfriedman@chromium.org

[commit-bot: I haz the power, 2014-03-21 00:26:41]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/yfriedman@chromium.org/204933002/20001

[commit-bot: I haz the power, 2014-03-21 03:15:52]

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

[commit-bot: I haz the power, 2014-03-21 03:15:52]

Try jobs failed on following builders:
  tryserver.chromium on mac_chromium_rel

[Yaron, 2014-03-21 04:51:32]

The CQ bit was checked by yfriedman@chromium.org

[commit-bot: I haz the power, 2014-03-21 04:51:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/yfriedman@chromium.org/204933002/20001

[commit-bot: I haz the power, 2014-03-21 12:20:27]

Change committed as 258544