Diagnose renderer-side crash with browser-side stack trace.

Diagnose renderer-side crash with browser-side stack trace.

This will log a crash dump without crashing the browser process, letting
us see how a main frame proxy is unexpectedly recreated.

BUG=575245
TEST=Crash dumps in RenderFrameHostManager::InitRenderFrame.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

Committed: https://crrev.com/5f94df51c0c36b3099632f82970fc846840204ad
Cr-Commit-Position: refs/heads/master@{#372772}

[Charlie Reis, 2016-01-31 06:41:11]

Description was changed from

==========
Diagnose renderer-side crash with browser-side stack trace.

This will log a crash dump without crashing the browser process, letting
us see how a main frame proxy is unexpectedly recreated.

BUG=575245
TEST=Crash dumps in RenderFrameHostManager::InitRenderFrame.
==========

to

==========
Diagnose renderer-side crash with browser-side stack trace.

This will log a crash dump without crashing the browser process, letting
us see how a main frame proxy is unexpectedly recreated.

BUG=575245
TEST=Crash dumps in RenderFrameHostManager::InitRenderFrame.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
==========

[Charlie Reis, 2016-01-31 06:44:03]

The CQ bit was checked by creis@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-31 06:44:13]

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

[commit-bot: I haz the power, 2016-01-31 08:22:10]

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

[commit-bot: I haz the power, 2016-01-31 08:22:11]

Dry run: This issue passed the CQ dry run.

[Charlie Reis, 2016-02-01 18:43:12]

creis@chromium.org changed reviewers:
+ nasko@chromium.org, rsesek@chromium.org

[Charlie Reis, 2016-02-01 18:43:13]

Nasko: Can you take a look?  Per comment 20 on https://crbug.com/575245, we're
likely getting to the crash from a FrameMsg_NewFrameProxy IPC, and this looks
like the only way for that to happen.  I'm curious how we can get into this
state, since I haven't been able to repro.  Hope we're getting close!

Robert: Can you review crash_keys.cc for owners?

[Robert Sesek, 2016-02-01 19:11:20]

lgtm

[nasko, 2016-02-01 19:47:57]

LGTM

[Charlie Reis, 2016-02-01 20:05:51]

The CQ bit was checked by creis@chromium.org

[commit-bot: I haz the power, 2016-02-01 20:06:40]

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

[commit-bot: I haz the power, 2016-02-01 21:45:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-01 21:46:35]

Description was changed from

==========
Diagnose renderer-side crash with browser-side stack trace.

This will log a crash dump without crashing the browser process, letting
us see how a main frame proxy is unexpectedly recreated.

BUG=575245
TEST=Crash dumps in RenderFrameHostManager::InitRenderFrame.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
==========

to

==========
Diagnose renderer-side crash with browser-side stack trace.

This will log a crash dump without crashing the browser process, letting
us see how a main frame proxy is unexpectedly recreated.

BUG=575245
TEST=Crash dumps in RenderFrameHostManager::InitRenderFrame.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

Committed: https://crrev.com/5f94df51c0c36b3099632f82970fc846840204ad
Cr-Commit-Position: refs/heads/master@{#372772}
==========

[commit-bot: I haz the power, 2016-02-01 21:46:36]

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