Issue metadata
Sign in to add a comment
|
Deadlock calling new WebView(context) on Android
Reported by
mor@contactspls.com,
Mar 14 2016
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Create a signed apk 2. Update from a previous signed apk 3. call from the UI thread: new WebView(context) What is the expected behavior? a webview is created What went wrong? Deadlock, see traces file attached Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? N/A Chrome version: 49.0.2623.91 Channel: stable OS Version: 5.1.1 Flash Version: - This happens only when updating a signed apk. Recreates almost consistently. The stack originates from MoPub's code, calling: userAgent = new WebView(context).getSettings().getUserAgentString(); See here: https://github.com/mopub/mopub-android-sdk/blob/f5154c436d761bea2c75b7fc2436efda6853b2e4/mopub-sdk/src/main/java/com/mopub/network/Networking.java#L133 but their code looks ok, and shouldn't deadlock. Waited for over 10 minutes multiple times, and it never returns, causing a white screen that isn't responsive.
,
Mar 14 2016
,
Mar 14 2016
All the async task background threads are blocked on UI thread in some ads code. Webview still stop blocking on async task background threads starting in m50 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mor@contactspls.com
, Mar 14 2016