Issue 2826213002: Prevent possible crash unregistering VR BroadcastReceiver

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2826213002: Prevent possible crash unregistering VR BroadcastReceiver (Closed)

Created:
3 years, 8 months ago by mthiesse

Modified:
3 years, 8 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/branch-heads/3071

Project:
chromium

Visibility:
Public.

Prevent possible crash unregistering VR BroadcastReceiver I only saw this crash once, and can't reproduce, but better safe than sorry. BUG=712823 Review-Url: https://codereview.chromium.org/2830463002 Cr-Commit-Position: refs/heads/master@{#465702} (cherry picked from commit 3eb6c9fae5bf061ac97480aa6670858c7c8cbc8f) Review-Url: https://codereview.chromium.org/2826213002 . Cr-Commit-Position: refs/branch-heads/3071@{#62} Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641} Committed: https://chromium.googlesource.com/chromium/src/+/31f6c164d4138dd81258d5afdefef59fd2abdefd

Created: 3 years, 8 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+5 lines, -1 line)			Patch
	M	chrome/android/java/src/org/chromium/chrome/browser/vr_shell/VrShellDelegate.java	View		1 chunk	+5 lines, -1 line	0 comments	Download

Total messages: 2 (1 generated)

mthiesse

3 years, 8 months ago (2017-04-19 19:34:01 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
31f6c164d4138dd81258d5afdefef59fd2abdefd.