service worker: Add crash keys for OnMessageReceived crash

service worker: Add crash keys for OnMessageReceived crash

We don't know why this crash is happening. One theory we
timed out a request, removed the listener, sent a stop
command, and meanwhile the response came back from the
worker. In that case we should see STOPPING or STOPPED
status. Also, log the IPC type for more clues.

BUG=625040
Committed: https://crrev.com/678557d52c9cf757fd2759067131418bb88de5e4
Cr-Commit-Position: refs/heads/master@{#404414}

[falken, 2016-07-08 09:10:58]

Description was changed from

==========
add crash key

BUG=
==========

to

==========
service worker: Add crash keys for OnMessageReceived crash

We don't know why this crash is happening. One theory we
timed out a request, removed the listener, sent a stop
command, and meanwhile the response came back from the
worker. In that case we should see STOPPING or STOPPED
status. Also, log the IPC type for more clues. 

BUG=625040
==========

[falken, 2016-07-08 09:11:52]

falken@chromium.org changed reviewers:
+ nhiroki@chromium.org, rsesek@chromium.org

[falken, 2016-07-08 09:11:53]

Please review.

[falken, 2016-07-08 09:12:09]

rsesek: crash keys
nhiroki: service worker

[nhiroki, 2016-07-08 09:45:04]

lgtm

[falken, 2016-07-08 14:44:54]

rsesek: please also hit the CQ checkbox if it lg to you, I hope to get it in
canary asap.

[Robert Sesek, 2016-07-08 15:00:20]

https://codereview.chromium.org/2134623002/diff/20001/chrome/common/crash_key...
File chrome/common/crash_keys.cc (right):

https://codereview.chromium.org/2134623002/diff/20001/chrome/common/crash_key...
chrome/common/crash_keys.cc:93: // //blimp/engine/app/blimp_engine_crash_keys.cc
Need to do this too.

[falken, 2016-07-08 15:09:09]

thanks

https://codereview.chromium.org/2134623002/diff/20001/chrome/common/crash_key...
File chrome/common/crash_keys.cc (right):

https://codereview.chromium.org/2134623002/diff/20001/chrome/common/crash_key...
chrome/common/crash_keys.cc:93: // //blimp/engine/app/blimp_engine_crash_keys.cc
On 2016/07/08 15:00:19, Robert Sesek wrote:
> Need to do this too.

Done.

[Robert Sesek, 2016-07-08 15:25:18]

lgtm

[falken, 2016-07-08 15:28:18]

The CQ bit was checked by falken@chromium.org

[falken, 2016-07-08 15:28:18]

The patchset sent to the CQ was uploaded after l-g-t-m from nhiroki@chromium.org
Link to the patchset: https://codereview.chromium.org/2134623002/#ps40001
(title: "blimp")

[commit-bot: I haz the power, 2016-07-08 15:28:52]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-08 16:48:01]

Description was changed from

==========
service worker: Add crash keys for OnMessageReceived crash

We don't know why this crash is happening. One theory we
timed out a request, removed the listener, sent a stop
command, and meanwhile the response came back from the
worker. In that case we should see STOPPING or STOPPED
status. Also, log the IPC type for more clues. 

BUG=625040
==========

to

==========
service worker: Add crash keys for OnMessageReceived crash

We don't know why this crash is happening. One theory we
timed out a request, removed the listener, sent a stop
command, and meanwhile the response came back from the
worker. In that case we should see STOPPING or STOPPED
status. Also, log the IPC type for more clues. 

BUG=625040
==========

[commit-bot: I haz the power, 2016-07-08 16:48:02]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-07-08 16:49:22]

Description was changed from

==========
service worker: Add crash keys for OnMessageReceived crash

We don't know why this crash is happening. One theory we
timed out a request, removed the listener, sent a stop
command, and meanwhile the response came back from the
worker. In that case we should see STOPPING or STOPPED
status. Also, log the IPC type for more clues. 

BUG=625040
==========

to

==========
service worker: Add crash keys for OnMessageReceived crash

We don't know why this crash is happening. One theory we
timed out a request, removed the listener, sent a stop
command, and meanwhile the response came back from the
worker. In that case we should see STOPPING or STOPPED
status. Also, log the IPC type for more clues.

BUG=625040

Committed: https://crrev.com/678557d52c9cf757fd2759067131418bb88de5e4
Cr-Commit-Position: refs/heads/master@{#404414}
==========

[commit-bot: I haz the power, 2016-07-08 16:49:23]

Patchset 3 (id:??) landed as
https://crrev.com/678557d52c9cf757fd2759067131418bb88de5e4
Cr-Commit-Position: refs/heads/master@{#404414}