Remove the Kasko based out of process browser hang instrumentation.

Remove the Kasko based out of process browser hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314
Committed: https://crrev.com/32d4643f0c60110d73c0ce8e01d0f88aa95bd8b0
Cr-Commit-Position: refs/heads/master@{#402189}

[manzagop (departed), 2016-06-22 14:18:37]

Description was changed from

==========
Remove the Kasko based out of process hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314
==========

to

==========
Remove the Kasko based out of process browser hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314
==========

[manzagop (departed), 2016-06-22 14:57:06]

manzagop@chromium.org changed reviewers:
+ pmonette@chromium.org

[manzagop (departed), 2016-06-22 14:57:07]

Hey Patrick,
Could you have a look?
Thanks,
Pierre

[Patrick Monette, 2016-06-22 21:48:17]

lgtm

[manzagop (departed), 2016-06-23 18:57:57]

manzagop@chromium.org changed reviewers:
+ jochen@chromium.org

[manzagop (departed), 2016-06-23 18:57:58]

Hi jochen@,

I'm looking for OWNERS' review for the first 4 files (pmonette@ is part of
chrome\chrome_watcher OWNERS).

Thanks!

Pierre

[jochen (gone - plz use gerrit), 2016-06-24 13:35:10]

lgtm

[manzagop (departed), 2016-06-27 14:22:52]

The CQ bit was checked by manzagop@chromium.org

[manzagop (departed), 2016-06-27 14:22:52]

The patchset sent to the CQ was uploaded after l-g-t-m from
pmonette@chromium.org
Link to the patchset: https://codereview.chromium.org/2086403002/#ps40001
(title: "Fix a comment")

[manzagop (departed), 2016-06-27 14:23:03]

Thanks for the review!

[commit-bot: I haz the power, 2016-06-27 14:23:14]

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-06-27 14:25:42]

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

[commit-bot: I haz the power, 2016-06-27 14:25:43]

Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[manzagop (departed), 2016-06-27 15:03:16]

The CQ bit was checked by manzagop@chromium.org

[manzagop (departed), 2016-06-27 15:03:17]

The patchset sent to the CQ was uploaded after l-g-t-m from
pmonette@chromium.org, jochen@chromium.org
Link to the patchset: https://codereview.chromium.org/2086403002/#ps60001
(title: "Merge")

[commit-bot: I haz the power, 2016-06-27 15:03:35]

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-06-27 15:52:15]

Description was changed from

==========
Remove the Kasko based out of process browser hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314
==========

to

==========
Remove the Kasko based out of process browser hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314
==========

[commit-bot: I haz the power, 2016-06-27 15:52:17]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-06-27 15:53:52]

Description was changed from

==========
Remove the Kasko based out of process browser hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314
==========

to

==========
Remove the Kasko based out of process browser hang instrumentation.

This CL removes the out-of-process browser hang instrumentation used to
capture 20s hangs and failed rendezvous crash reports in one-off canary
releases. The Kasko reporter is deprecated, and CrashPad does not yet
support the use case.

The plan is to restore this functionality once CrashPad supports it.

BUG=622314

Committed: https://crrev.com/32d4643f0c60110d73c0ce8e01d0f88aa95bd8b0
Cr-Commit-Position: refs/heads/master@{#402189}
==========

[commit-bot: I haz the power, 2016-06-27 15:53:54]

Patchset 4 (id:??) landed as
https://crrev.com/32d4643f0c60110d73c0ce8e01d0f88aa95bd8b0
Cr-Commit-Position: refs/heads/master@{#402189}

[grt (UTC plus 2), 2017-09-15 08:14:31]

grt@chromium.org changed reviewers:
+ grt@chromium.org

[grt (UTC plus 2), 2017-09-15 08:14:32]

base/win/wait_chain* appears to be unused since this CL landed. can it be
removed as well, or is it being used in some other project somehow?

[manzagop (departed), 2017-09-15 14:05:49]

On 2017/09/15 08:14:32, grt (UTC plus 2) wrote:
> base/win/wait_chain* appears to be unused since this CL landed. can it be
> removed as well, or is it being used in some other project somehow?

Yes, it can be removed. Patrick can chime in if I'm wrong.