New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 807552 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

Crash caused by IllegalArgumentException due to Receiver not registered at org.chromium.content.browser.accessibility.LollipopWebContentsAccessibility

Reported by davi...@gmail.com, Jan 31 2018

Issue description

Device name: Many devices, as per Google Play Console

From "Settings > About Chrome"
Application version: 63.0.3239.111
Operating system: >= Android 5.0.1

URLs (if applicable):

Steps to reproduce:
(1) Open WebView from code invoked within a BroadcastReceiver
(2) Wait for Activity to be destroyed
(3) App crashes with java.lang.IllegalArgumentException: Receiver not registered: org.chromium.content.browser.accessibility.LollipopWebContentsAccessibility$1 at LollipopWebContentsAccessibility.onDetachedFromWindow

We have started seeing many crashes in our apps due to this error. First one happened on Dec 27 but they are skyrocketting since Jan 25.

We suspect it is related to this fix https://chromium-review.googlesource.com/c/chromium/src/+/729145, since it's possible for the receiver to not be registered (as the modified code checks with a try-catch block), but no check is performed when doing the unregister, which will fail and cause a crash if there was no previous register.


 
Components: Mobile>WebView
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Labels: WV-Triaged Needs-Feedback
@davidst: Thanks for the report!!

Looks like your'e using old WebView version, could you please update your WebView to the latest version #64.0.3282.137 and check if you still face the issue?

Thanks!!


Comment 3 by davi...@gmail.com, Feb 1 2018

Problem was finally on our side, we were reusing the same Context for different activities.

1) Activity A obtains a new Context at attachBaseContext()
2) Activity B is launched and previous Context is received, and internally their receivers are somehow cleaned 
3) Go back to Activity A
4) Go back again. onDestroy() for Activity A triggers an unregister that fails because there are no receivers any longer
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 1 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by boliu@chromium.org, Feb 1 2018

Mergedinto: 780261
Status: Duplicate (was: Unconfirmed)
zillow presumably?

webview will ask for the application context in the next release, which also works around this issue

Sign in to add a comment