base::debug::DumpWithoutCrashing does not work in the renderer process on Android. |
||||
Issue descriptionDiscovered while working on https://codereview.chromium.org/1808473002/ -- no crash dumps are being produced in recent history for the renderer process: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20OMIT%20RECORD%20IF%20SUM(CrashedStackTrace.StackFrame.FunctionName%3D%27base%3A%3Adebug%3A%3ADumpWithoutCrashing%27)%20%3D%200&ignore_case=false&enable_rewrite=true&omit_field_name=CrashedStackTrace.StackFrame.FunctionName&omit_field_value=base%3A%3Adebug%3A%3ADumpWithoutCrashing&omit_field_opt=%3D&stbtiq=&reportid=&index=0 There are no reports since Chrome 42 || 44 for renderer-initiated dumps.
,
Apr 14 2016
At a quick glance the issue seems that on Android the renderer initializes in InitNonBrowserCrashReporterForAndroid, which does NOT seem to call PostEnableBreakpadInitialization(), which in turn is the thing that sets SetDumpWithoutCrashingFunction(&DumpProcess);
,
Apr 17 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 17 2017
Probably we should find some way to make this a more obvious failure at least.
,
Apr 18 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsesek@chromium.org
, Apr 14 2016