This was supposedly fixed in crbug.com/710121 though that fix went into 58.0.3029.68, and there are reports of this crash in 58.0.3029.83.


-debugger_posix.cc:221 )	base::debug::BreakDebugger()
-logging.cc:759 )	logging::LogMessage::~LogMessage()
-jni_android.cc:243 )	base::android::CheckException(_JNIEnv*)
-jni_generator_helper.h:42 )	content::DateTimeChooserAndroid::ShowDialog(...)
-web_contents_impl.cc:3745 )	content::WebContentsImpl::OnOpenDateTimeDialog(content::RenderViewHostImpl*, ViewHostMsg_DateTimeDialogValue_Params const&)
-ipc_message_templates.h:40 )	content::WebContentsImpl::OnMessageReceived(content::RenderViewHostImpl*, IPC::Message const&)
-render_view_host_impl.cc:732 )	content::RenderViewHostImpl::OnMessageReceived(IPC::Message const&)
-render_widget_host_impl.cc:539 )	content::RenderWidgetHostImpl::OnMessageReceived(IPC::Message const&)
-render_process_host_impl.cc:2081 )	content::RenderProcessHostImpl::OnMessageReceived(IPC::Message const&)
-ipc_channel_proxy.cc:329 )	IPC::ChannelProxy::Context::OnDispatchMessage(IPC::Message const&)
-callback.h:68 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
-message_loop.cc:423 )	base::MessageLoop::RunTask(base::PendingTask*)
-message_loop.cc:434 )	base::MessageLoop::DeferOrRunPendingTask(base::PendingTask)
-message_loop.cc:527 )	base::MessageLoop::DoWork()
-message_pump_android.cc:44 )	Java_org_chromium_base_SystemMessageHandler_nativeDoRunLoopOnce


Crash.corp URL for 58:
https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.magic_signature_1.name%20CONTAINS%20%27%5BAndroid%20Java%20Exception%5D%27%20AND%20product.name%3D%27AndroidWebView%27%20AND%20product.Version%20CONTAINS%20%2758.0.3%27%20AND%20special_protos.user_feedback.mobile_data.crash_data.exception_class_name%3D%27Native%20crash%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BAndroid%20Java%20Exception%5D%20content%3A%3ADateTimeChooserAndroid%3A%3AShowDialog%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D


The thread where this is run is backed by Java.
I believe this is not handled by the app at all though - so any exceptions here should have been thrown by us rather than by the app.