Same crashing here on Nexus 5X on Android System Webview: 48.0.2564.106.

Now I deleted this webview, and restore to the factory's default webview version (44.0.2403.117) and the crash does NOT happen anymore.

Deleted: crash.txt 352 KB

crash.txt 352 KB View Download

Hi, how soon can this be fixed?

As now I have an unknown number of customers upgraded to this webview will simply encounter webview crash from within our app, it would be very challenging for us to tackle this.

I have no idea how to symbolize webview crashes, let's see what WebView folks say.

just tried the link in the initial post on my Nexus 5x Android 6 + WebView 51 combination and it did not crash.

jeffrey.garcia@: did you try the same link or was it something else?.. (from looking at the logs)

It is not the link from lannyte.
My company app which runs a lot features using webview, and crashes when on webview 48.0.2564.106 of nexus 5x

jeffrey.garcia: crash you reported is a dup of  crbug.com/541145 

Both crashes in original report. Symbolized stack below.

I think this is a long standing crash, but no one understands how it happens. I think torne's last analysis was that blink is being restarted after teardown, and we are not sure how that can happen at all.

lannytest1: Can you share the app and repro steps? We'd be very interested in actually producing this ourselves, even if it's not consistent.

Operating system: Android
                  htc/htc_asia_tw/htc_m8:6.0/MRA58K/689733.2:user/release-keys
CPU: armv7l
     4 CPUs

Crash reason:
Crash address: 0x0
Process uptime: not available

Thread 0 (crashed)
 0  libwebviewchromium.so!WTF::initialize [WTF.cpp : 49 + 0x2]

    Found by: given as instruction pointer in context
 1  libwebviewchromium.so!blink::initializeWithoutV8 [WebKit.cpp : 179 + 0x19]

    Found by: call frame info
 2  libwebviewchromium.so!blink::initialize [WebKit.cpp : 111 + 0x3]

    Found by: call frame info
 3  libwebviewchromium.so!content::RenderThreadImpl::EnsureWebKitInitialized [render_thread_impl.cc : 1127 + 0x7]

    Found by: call frame info
 4  libwebviewchromium.so!android_webview::AwContentRendererClient::RenderThreadStarted [aw_content_renderer_client.cc : 72 + 0x7]

    Found by: call frame info
 5  libwebviewchromium.so!content::RenderThreadImpl::Init [render_thread_impl.cc : 691 + 0x3]

    Found by: call frame info
 6  libwebviewchromium.so!content::RenderThreadImpl::RenderThreadImpl [render_thread_impl.cc : 583 + 0x3]

    Found by: call frame info
 7  libwebviewchromium.so!content::RenderThreadImpl::RenderThreadImpl [render_thread_impl.cc : 584 + 0x9]

    Found by: call frame info
 8  libwebviewchromium.so!content::RenderThreadImpl::Create [render_thread_impl.cc : 559 + 0x7]

    Found by: call frame info
 9  libwebviewchromium.so!base::Thread::ThreadMain [thread.cc : 242 + 0x3]

    Found by: call frame info
10  libwebviewchromium.so!base::::ThreadFunc [platform_thread_posix.cc : 64 + 0x7]

    Found by: call frame info
11  libc.so + 0x41f47

    Found by: call frame info
12  libc.so + 0x41f27

    Found by: stack scanning
13  libc.so + 0x41f27

    Found by: stack scanning
14  libc.so + 0x190b3

    Found by: stack scanning
15  libwebviewchromium.so + 0x2fc5a7

    Found by: stack scanning

boliu: pls try my company app
https://play.google.com/store/apps/details?id=com.htsu.hsbcpersonalbanking

We uses a lot webview to our features, after install, go straight to accept the license agreement then select country as HK, after downloading the country assets you will be at the app home screen, choose the Branch locator function, with the captioned webview version on nexus 5g, you can easily hit the crash playing around.

We tried a few other devices with same webview version, may not crash but the webview renderung will look clunky.

I know the html code of that function is not great but it just behaves fine in the stable webview version in this link
http://googlechromereleases.blogspot.hk/search/label/Android%20WebView?m=1

Hope the above info help isolating the problem

jeffrey.garcia: Your crash is  crbug.com/541145 . It's workaround in m49 already.

> jeffrey.garcia: Your crash is  crbug.com/541145 . It's workaround in m49 already.

ie it should stop crashing in m49

I am confused, are you referring the version auggested 48.0.2564.95 in the bottom of the thread 541145?

Cause the issue I have here is the webview version which is even newer 48.0.2564.106

Should be fixed in 49.0.2623.* or later. It's not rolled out to everyone yet. You can try it with webview beta: https://plus.google.com/communities/105434725573080290360

Okay tried now, the beta go straight to version 50.

Crash is gone but the page rendering is horrible, now even more clunky and I can heavy delay during animation with shadow like slow motion

Well I am okay to live with bug in beta, but then the crashing  M48.x shouldn't go live in play store if it's never stable or should be pull down

Now I have an unknown number of customers using the crash M48 and probably flooding our hotline or rating a 1-star comment with the app

Just found the new version 49.0.2635.105 is released on Google Play and installed it and all issues gone.

Thanks, that makes me put it to 5-stars again!

Original reporter doesn't seem to be responding anymore