Verify that FetchEvent::m_request holds same-thread reference.

Verify that FetchEvent::m_request holds same-thread reference.

To diagnose instability seen during GCs of FetchEvents, instrument
the m_request member, checking that we only create event object containing
references to Requests that reside in the current thread's heap.

R=
BUG=655926
Committed: https://crrev.com/3d5b1a43aeb21176af2d264d8ec399916e29c4cd
Cr-Commit-Position: refs/heads/master@{#440475}

[sof, 2016-12-22 16:36:15]

The CQ bit was checked by sigbjornf@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2016-12-22 16:36:24]

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

[sof, 2016-12-22 16:43:06]

sigbjornf@opera.com changed reviewers:
+ haraken@chromium.org

[sof, 2016-12-22 16:43:06]

please take a look.

Same theory for this one as in https://codereview.chromium.org/2589333005/ -
m_request ends up being set with a Request belonging to another thread when
created from script.

[haraken, 2016-12-22 17:35:07]

LGTM

[commit-bot: I haz the power, 2016-12-22 19:40:12]

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

[commit-bot: I haz the power, 2016-12-22 19:40:13]

Dry run: This issue passed the CQ dry run.

[sof, 2016-12-22 19:41:02]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2016-12-22 19:41:19]

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-12-22 19:45:25]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1482435662004020, "parent_rev":
"169f887c2ae736f9c10c109a24a16bf446170d01", "commit_rev":
"debe7b46ada6844171b3eef3573f93c3bc0de941"}

[commit-bot: I haz the power, 2016-12-22 19:45:56]

Description was changed from

==========
Verify that FetchEvent::m_request holds same-thread reference.

To diagnose instability seen during GCs of FetchEvents, instrument
the m_request member, checking that we only create event object containing
references to Requests that reside in the current thread's heap.

R=
BUG=655926
==========

to

==========
Verify that FetchEvent::m_request holds same-thread reference.

To diagnose instability seen during GCs of FetchEvents, instrument
the m_request member, checking that we only create event object containing
references to Requests that reside in the current thread's heap.

R=
BUG=655926

Review-Url: https://codereview.chromium.org/2594423002
==========

[commit-bot: I haz the power, 2016-12-22 19:45:58]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-22 19:48:20]

Description was changed from

==========
Verify that FetchEvent::m_request holds same-thread reference.

To diagnose instability seen during GCs of FetchEvents, instrument
the m_request member, checking that we only create event object containing
references to Requests that reside in the current thread's heap.

R=
BUG=655926

Review-Url: https://codereview.chromium.org/2594423002
==========

to

==========
Verify that FetchEvent::m_request holds same-thread reference.

To diagnose instability seen during GCs of FetchEvents, instrument
the m_request member, checking that we only create event object containing
references to Requests that reside in the current thread's heap.

R=
BUG=655926

Committed: https://crrev.com/3d5b1a43aeb21176af2d264d8ec399916e29c4cd
Cr-Commit-Position: refs/heads/master@{#440475}
==========

[commit-bot: I haz the power, 2016-12-22 19:48:22]

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