Dynamic module uncaught exception (crash) reporting |
||||
Issue descriptionA dynamically loaded module may throw an uncaught exception (crash) and we want the module to be able to report on that exception.
,
Jul 20
See go/qwark-crash-handling for the design.
,
Sep 6
As a client side seems more complex than welcome while Chrome is crashing, we're now exploring what we can do server side: go/qwark-crashes-server-side
,
Sep 10
,
Sep 14
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e8664ecd88d0e19af8a1e4e37b66c6cbb15fb097 commit e8664ecd88d0e19af8a1e4e37b66c6cbb15fb097 Author: Michael van Ouwerkerk <mvanouwerkerk@google.com> Date: Fri Sep 14 10:39:11 2018 Tweak dynamic module crash key values for deobfuscation server There's a sample crash report at crash/29c8dbdcacdc72b1 see Fields > Product data > loaded_dynamic_module Bug: 865935 Change-Id: Iceef1eea20064565e08712cb087850818a34f581 Reviewed-on: https://chromium-review.googlesource.com/1216363 Reviewed-by: Peter Conn <peconn@chromium.org> Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Cr-Commit-Position: refs/heads/master@{#591319} [modify] https://crrev.com/e8664ecd88d0e19af8a1e4e37b66c6cbb15fb097/chrome/android/java/src/org/chromium/chrome/browser/customtabs/dynamicmodule/ModuleLoader.java
,
Dec 14
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mvanouwe...@chromium.org
, Jul 20