Null check secondary_pointer_down_event_

Null check secondary_pointer_down_event_

There are some crash reports in android webview that suggests this
pointer is null and used. In android webview, the app gets the touch
events first, so can modify or drop events however they want. That may
be the reason certain assumptions holds in chrome, but not in webview.

Assuming that's the case, just add null checks before use.

BUG=675772
Committed: https://crrev.com/f701a9837b92d3259e9792c24a9de338fb9d8352
Cr-Commit-Position: refs/heads/master@{#440960}

[boliu, 2016-12-21 19:29:32]

boliu@chromium.org changed reviewers:
+ tdresser@chromium.org

[boliu, 2016-12-21 19:29:33]

ptal, bug has more context

[boliu, 2016-12-21 19:29:38]

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

[commit-bot: I haz the power, 2016-12-21 19:30:26]

Dry run: 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-21 20:36:54]

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

[commit-bot: I haz the power, 2016-12-21 20:36:55]

Dry run: This issue passed the CQ dry run.

[tdresser, 2016-12-24 15:18:58]

LGTM as a short term fix. Let's still try to identify cases where WebView is
doing goofy things higher in the stack, and clean up the event stream as early
as possible.

[boliu, 2016-12-29 15:43:04]

The CQ bit was checked by boliu@chromium.org

[commit-bot: I haz the power, 2016-12-29 15:43:09]

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-29 16:25:32]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483026184892210, "parent_rev":
"45584a79bec546537027818187f86f9dd0393e57", "commit_rev":
"ddfc0e7b7c75295e03662e8c6a18a2bc775ca78d"}

[commit-bot: I haz the power, 2016-12-29 16:26:01]

Description was changed from

==========
Null check secondary_pointer_down_event_

There are some crash reports in android webview that suggests this
pointer is null and used. In android webview, the app gets the touch
events first, so can modify or drop events however they want. That may
be the reason certain assumptions holds in chrome, but not in webview.

Assuming that's the case, just add null checks before use.

BUG=675772
==========

to

==========
Null check secondary_pointer_down_event_

There are some crash reports in android webview that suggests this
pointer is null and used. In android webview, the app gets the touch
events first, so can modify or drop events however they want. That may
be the reason certain assumptions holds in chrome, but not in webview.

Assuming that's the case, just add null checks before use.

BUG=675772

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

[commit-bot: I haz the power, 2016-12-29 16:26:02]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2017-01-02 15:52:24]

Description was changed from

==========
Null check secondary_pointer_down_event_

There are some crash reports in android webview that suggests this
pointer is null and used. In android webview, the app gets the touch
events first, so can modify or drop events however they want. That may
be the reason certain assumptions holds in chrome, but not in webview.

Assuming that's the case, just add null checks before use.

BUG=675772

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

to

==========
Null check secondary_pointer_down_event_

There are some crash reports in android webview that suggests this
pointer is null and used. In android webview, the app gets the touch
events first, so can modify or drop events however they want. That may
be the reason certain assumptions holds in chrome, but not in webview.

Assuming that's the case, just add null checks before use.

BUG=675772

Committed: https://crrev.com/f701a9837b92d3259e9792c24a9de338fb9d8352
Cr-Commit-Position: refs/heads/master@{#440960}
==========

[commit-bot: I haz the power, 2017-01-02 15:52:25]

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