Issue metadata
Sign in to add a comment
|
Mac PWAs: Report crashes of the AppShim process |
||||||||||||||||||||||
Issue descriptionWe get no crash reports for the AppShim process in chromecrash/ (as far as I can tell). Since we are now doing a fair amount of work in this process, we should make sure that we are gathering crash reports from this process. For background on the AppShim process, see this document https://docs.google.com/document/d/1ps3-_5RFQu37x1fuYY79Z5_WnpPPFqjGXksxZDahgiI/edit?usp=sharing Or ChromeAppModeStart_v4: https://cs.chromium.org/chromium/src/chrome/app_shim/chrome_main_app_mode_mac.mm?rcl=8a6cc166e9b9856c151493d807c080774200c126&l=588 What is necessary to start generating reports from this process?
,
Oct 12
True, we don't come through ChromeMain. We are also not a child process -- we are a peer -- we dlopen() chrome, and we establish a mojo connection. Simply adding the lines crash_reporter::SetCrashReporterClient(new ChromeCrashReporterClient); crash_reporter::InitializeCrashpad(true /* initial_client */, "" /* process_type */); seems to not crash at least. Not sure it actually sets things up appropriately. If I set process_type to something like "appshim" then it's not happy. Is there any sort of testing I can do to see if that works? IIUC, this would report all appshim crashes as browser crashes (which we would want to differentiate somehow).
,
Nov 6
,
Nov 7
,
Nov 7
,
Dec 4
,
Dec 5
,
Dec 11
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1c9f89a06fba506b4efdb40fa3407976012a550a commit 1c9f89a06fba506b4efdb40fa3407976012a550a Author: Sidney San Martín <sdy@chromium.org> Date: Tue Dec 11 19:46:25 2018 Initialize Crashpad to catch app shim crashes. Bug: 893821 Change-Id: Ic2ff92577d35250fbe773ff6b80918da33d57155 Reviewed-on: https://chromium-review.googlesource.com/c/1365955 Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Sidney San Martín <sdy@chromium.org> Cr-Commit-Position: refs/heads/master@{#615629} [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/app/chrome_crash_reporter_client.cc [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/app/chrome_crash_reporter_client.h [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/app/chrome_main_delegate.cc [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/app_shim/BUILD.gn [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/app_shim/DEPS [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/app_shim/chrome_main_app_mode_mac.mm [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/chrome/test/base/chrome_test_launcher.cc [modify] https://crrev.com/1c9f89a06fba506b4efdb40fa3407976012a550a/components/crash/content/app/crashpad.cc
,
Dec 11
Should be all set, setting a reminder to verify.
,
Dec 13
The NextAction date has arrived: 2018-12-13
,
Dec 13
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mark@chromium.org
, Oct 10