@tfs3builds.android: Thanks for the report!!

Could you please update to Chrome or WebView to latest version #65.0.3325.109 and check if you still face the issue?

Thanks!!

I am trying to, we execute our tests in the xamarin test cloud. I sent a request to the support if they could update my devices.

Thank you for providing more feedback. Adding the requester to the cc list.

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

The crash address of this report is not in any mapped code. That might mean that it is in native code generated for JS by V8, but there's no way to determine what that might be.

I'm afraid that without a means to reproduce this there's nothing we can do further.

If you have more complete logs you could try looking above the microdump for any V8 logging.

Sometimes I also get a stack trace like this, where I do not know what it means when there is the statement "Microdump skipped uninteresting"

Deleted: loooog.txt 90.6 KB

loooog.txt 90.6 KB View Download

Hi got another stack trace this time from a more recent version of chrome.
The stacktrace before the crash is comepletely different.
Could you please make clear if chrome crashed because of something else or if it crashes by itself? 

Deleted: loooog.txt 24.8 KB

loooog.txt 24.8 KB View Download

In #6, "Microdump skipped: uninteresting" means we didn't generate a microdump because there's no chromium code on the stack (i.e. the crash is almost definitely not related to webview). You can see the stack trace from debuggerd later in the log that shows this:
#00 pc 00006d50 /vendor/lib/libnvglsi.so (_nv002glsi+23)
#01 pc 005d2fe7 /vendor/lib/libglcore.so (__eglGetGLSDrawable(__WINdrawablePrivateRec*)+22)
#02 pc 005c5e17 /vendor/lib/libglcore.so (UpdateDrawableClient(__GLdrawablePrivateRec*, unsigned char)+138)
#03 pc 005c6d95 /vendor/lib/libglcore.so (__winImpUpdateDrawable(__GLdrawablePrivateRec*)+76)
#04 pc 00641fbd /vendor/lib/libglcore.so (SlcCheckCounters(__GLNVstateRec*, __GLdrawablePrivateRec*, __GLdrawablePrivateRec*)+88)
#05 pc 006421ad /vendor/lib/libglcore.so (__glNVSharedLibraryCommand(__GLNVstateRec*, __GLNVoperationRec*)+212)
#06 pc 0061ed6f /vendor/lib/libglcore.so (__glNVFlush+266)
#07 pc 0061f011 /vendor/lib/libglcore.so (__glNVFinish+260)
#08 pc 005e177b /vendor/lib/libglcore.so (nvDestroyContext(__GLinterfaceRec*)+130)
#09 pc 005d161f /vendor/lib/libglcore.so (NvEglDeleteContext+194)
#10 pc 0000731d /vendor/lib/egl/libGLESv2_tegra.so (NvGlImplContextDestroy+12)
#11 pc 0003e305 /vendor/lib/egl/libEGL_tegra.so (NvEglFreeObject(NvEglObjectRec*)+24)
#12 pc 0003e393 /vendor/lib/egl/libEGL_tegra.so (NvEglHandleDeinit()+62)
#13 pc 0000d6ed /vendor/lib/egl/libEGL_tegra.so (NvEglSystem_Deinit()+44)
#14 pc 00046f04 /vendor/lib/egl/libEGL_tegra.so (__atexit_handler_wrapper+36)

The output inbetween looks like you're using some other custom crash reporting system as well - maybe that's interfering?

The log in #7 is hard to work with because it's not in the standard format from adb logcat that our automated tools expect; how are you getting this? Also, please don't cut off the log immediately after the microdump - include all the debuggerd crash output as well, as this is also useful.