kmg@google.com chrome-stability-core@google.com Number of ChildProcessHost.BindHostReceiver requests coalesced into a single batched BindHostReceivers() IPC from a child process to the browser. Recorded once per flush. A value of 1 means no coalescing happened for that flush; larger values quantify how effectively the per-receiver bind IPCs are batched during process startup. wfh@chromium.org chrome-stability-core@google.com Recorded when a crash occurs in a Utility process. On crash, the exit code will indicate the exception code of the crash. wfh@chromium.org chrome-stability-core@google.com Count of child utility process crashes, bucketed by the hash of their process name. The process name is typically the service name of the mojo service. Recorded when a Utility process crashes. wfh@chromium.org chrome-stability-core@google.com Count of child process crashes grouped by process type. wfh@chromium.org Count of child process abnormal channel disconnects that are not classified and reported because we took the exit code too early. Grouped by process type. wfh@chromium.org chrome-stability-core@google.com Count of child process kills grouped by process type. wfh@chromium.org Count of child utility process launches, bucketed by the hash of their process name. The process name is typically the service name of the mojo service. wfh@chromium.org chrome-stability-core@google.com A platform-specific error code returned from the attempt to launch a Utility process. Recorded when a Utility process fails to launch. wfh@chromium.org chrome-stability-core@google.com Count of child utility process launch failures, bucketed by the hash of their process name. The process name is typically the service name of the mojo service. Recorded when a Utility process fails to launch. wfh@chromium.org chrome-stability-core@google.com An extended Windows error code returned from GetLastError when failing to launch a utility process. Recorded when a Utility process fails to launch on Windows. olivierli@chromium.org fdoray@chromium.org The time elapsed between the creation and destruction of a utility process. Recorded when the process is recorded as destroyed in PerformanceManager. wfh@chromium.org chrome-stability-core@google.com The exit codes for crashed extension processes. Note: Due to https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. wfh@chromium.org chrome-stability-core@google.com The exit codes for crashed renderer processes. Note: Due to https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. smaier@chromium.org crashpad-dev@chromium.org The reason that an ANR upload was skipped. jperaza@chromium.org crashpad-dev@chromium.org The reason that a crash report entered the upload pending state. jperaza@chromium.org crashpad-dev@chromium.org The size of a crash report minidump on disk when captured. jperaza@chromium.org crashpad-dev@chromium.org Logs whether a crash uploaded succeeded or failed. justincohen@chromium.org crashpad-dev@chromium.org The error codes from [NSURLConnection sendSynchronousRequest:returningResponse:error:] jperaza@chromium.org crashpad-dev@chromium.org The reason that a crash report upload was skipped. jperaza@chromium.org crashpad-dev@chromium.org The outcome of execution of the Crashpad exception handler. mark@chromium.org crashpad-dev@chromium.org The exception code encountered in a crash on Mac OS X. jperaza@chromium.org crashpad-dev@chromium.org The exception code encountered in a crash on Windows. jperaza@chromium.org crashpad-dev@chromium.org A count of the number of exceptions handled by Crashpad with two buckets for starting and finishing. mark@chromium.org crashpad-dev@chromium.org The exception code encountered for a crash of the crash handler process on Mac OS X. jperaza@chromium.org crashpad-dev@chromium.org The exception code encountered for a crash of the crash handler process on Windows. Kept as a diagnostic metric. jperaza@chromium.org crashpad-dev@chromium.org Handler start/crash/exit events. justincohen@chromium.org crashpad-dev@chromium.org Records key id when id has an invalid sizein an intermediate dump. justincohen@chromium.org crashpad-dev@chromium.org Records key id when id is missing in an intermediate dump. gjc@google.com chrome-loading@google.com Records whether a process killed because of KillType is a spare renderer and the spare renderer existence. Recorded when a child process exits and the kill type in the ChildProcessTerminationInfo matches KillType. KillType Details: {KillType} shaktisahu@chromium.org src/components/minidump_uploader/OWNERS Records the time (uptimeMillis) taken by a minidump uploading task to complete. Recorded when the task finished callback is invoked. boliu@chromium.org ssid@chromium.org wnwen@chromium.org Individual enum counts specific conditions of child process terminations. There are too many individual states to enumerate into a single histogram, so this effectively does the aggregration that normally happens on the server side in the client instead. The benefit is this is easily extensible in the future, and downside is that it does not allow additional server side analysis. Note a single child process termination may fall into multiple enums. wnwen@chromium.org src/components/minidump_uploader/OWNERS Records the number of non-simulated minidumps processed by Crashpad, split by process type. This metric is similar to one that could be computed server-side based on received crash uploads; but the client-side metric also includes any minidumps that were not successfully uploaded. wnwen@chromium.org Counts renderer crashes including OOMs. Android only. Mirrors old stability proto renderer crashes. boliu@chromium.org ssid@chromium.org wnwen@chromium.org Reason given by Android ActivityManager for the exit of the process, only recorded in Android R+. Recorded on the next browser startup for browser exits, or right after the process died for child processes. Records API failed when the ActivityManager does not return a reason. {AndroidProcessExitReasons} creis@chromium.org jamescook@chromium.org Count of processes killed by chrome/browser because they sent an IPC that couldn't be properly handled. Categories are the reasons (code locations) for the kills. jam@chromium.org jamescook@chromium.org Count of child processes killed because they sent an IPC that couldn't be properly handled. Categories are the reasons (code locations) for the kills. rdevlin.cronin@chromium.org extensions-core@chromium.org Count of extension processes killed because they sent an IPC that couldn't be properly handled. Categories are the reasons (code locations) for the kills. mcnee@chromium.org wjmaclean@chromium.org Count of processes killed because they sent a bad IPC that couldn't be properly handled. Categories are the reasons (code locations) for the kills. Warning: this histogram was expired from M85 to M97; data may be missing. creis@chromium.org jamescook@chromium.org Count of processes killed because they sent a bad IPC that couldn't be properly handled. Categories are the reasons (code locations) for the kills. Warning: this histogram was expired from M85 to M97; data may be missing. siggi@chromium.org chrome-stability-core@google.com Records the exit code of the browser process (on Windows) from the previous launch. On crash, the exit code will indicate the exception code of the crash. This is emitted in stability data with the first report on a subsequent launch. Note: Due to https://crbug.com/805754, the enum labels for RESULT_CODE_* are off by 1 for M56 and earlier. kawasin@google.com boliu@chromium.org Logs whether a page with a crashed subframe is eligible to be discarded at DiscardPageWithCrashedSubframePolicy. Logged once per subframe process crash. kawasin@google.com boliu@chromium.org Logs whether a page with a crashed subframe will be marked for reload. The logic is implemented as ReloadHiddenTabsWithCrashedSubframes feature but DiscardPageWithCrashedSubframePolicy logs the result with the same logic. This is a supplementary metrics to understand Stability.ChildFrameCrash.PageEligibleToDiscard metrics better. Logged once per subframe process crash. alexmos@chromium.org boliu@chromium.org lukasza@chromium.org Logs the reason that a crashed subframe was shown. Logged at most once per crash, and only if the subframe was hidden when it crashed and became visible later. alexmos@chromium.org boliu@chromium.org Logs whether or not a tab is marked for reload when a cross-process subframe crashes. Logged once per subframe process crash. alexmos@chromium.org boliu@chromium.org Logs the visibility of a subframe when a subframe process crashes and the corresponding tab is marked for reload. This indicates whether the crashed subframe was visible or scrolled out of view at the time of crash. alexmos@chromium.org boliu@chromium.org lukasza@chromium.org Logged after detecting that a sad subframe is shown (logged at most once per crash). aattar@google.com chrome-stability-core@google.com Records the outcome of a user's attempt to reload a tab that was terminated due to system commit limits (CHROME_RESULT_CODE_TERMINATED_BY_OTHER_PROCESS_ON_COMMIT_FAILURE). Windows only. At most one sample is recorded per commit-limit termination. The exact emission points for each bucket are: - Success: A hidden tab was discarded after the termination and, once made visible again, its reload navigation committed without an error page. - Failed: Repeated OOM / Other Error: The renderer exited again (with a commit-limit or other abnormal exit, respectively) while the recovery was being tracked. - Failed: Hidden Tab Not Discarded: The hidden tab was not discarded and became visible again, which shows a sad tab. Unrecorded cases (no sample recorded): Navigating to a different URL, hiding the tab during tracking, or closing the tab (normal termination). aattar@google.com chrome-stability-core@google.com Records the visibility of a tab when its renderer was terminated due to system commit limits (CHROME_RESULT_CODE_TERMINATED_BY_OTHER_PROCESS_ON_COMMIT_FAILURE). Logged once at termination time. Windows only. rkaplow@chromium.org src/base/metrics/OWNERS chrome-analysis-team@google.com Collects various counters related to stability. For the crash-related buckets, see https://chromium.googlesource.com/chromium/src/+/main/docs/stability.md for details on what aspects of stability are being measured and how, how the measured aspects reflect (or don't reflect) crashes, and how they relate to crash reports in the Crash database. In M129 we are more accurately tracking renderer process launch failures, and expect to find a significant spike in volume for this bucket. nasko@chromium.org Logged at the time when a complex debugging scenario is encountered. The enum value is the type of scenario encountered. This metric will give us two benefits: 1. It will tell us the magnitute of the scenario being debugged since crash reports are throttled client side and cannot presently expess magnitude. 2. If the client is configured to report traces based on this metric, it will upload Chrometto trace for analysis by developers. dcheng@chromium.org wfh@chromium.org adkushwa@microsoft.com Keeps a count of number of times uploading the dump was throttled when calling DumpWithoutCrashing. fdoray@chromium.org catan-team@chromium.org Counts "pageloads" by type. This is recorded when a page stops loading, i.e. from WebContentsObserver::DidStopLoading. The sum of all buckets of this histogram should be equal to the "Total pageloads" shown on Stability dashboards and can be used to diagnose changes to this value. michaelbai@chromium.org src/base/metrics/OWNERS The number of unsent files. Emitted when the stability is recorded. michaelbai@chromium.org src/base/metrics/OWNERS The total number of samples that will be lost if ASSOCIATE_INTERNAL_PROFILE hasn't been enabled since the previous stability recorded. This is different than the previous browser run because one file was just uploaded before the stability is recorded. davidbienvenu@chromium.org jessemckenna@google.com Number of times a browser crash was detected, where the browser was last known to be alive in a Windows system session that terminated abnormally. justincohen@chromium.org olivierrobin@chromium.org Records whether Crashpad init was successful. Recorded on every app startup. justincohen@chromium.org bling-fundamentals@google.com Recorded when the app is foregrounded. Records what action is taken after an unclear shutdown (likely a crash). justincohen@chromium.org bling-fundamentals@google.com The number of tabs opened in the previous session when the app starts after {Event}. Can be used to understand if there is a correlation between increase of number of tabs and decline in stability. iOS Only. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. olivierrobin@chromium.org justincohen@chromium.org Recorded on iOS when applicationWillTerminate callback is called when app is in the foreground. When this happens the app will not write clean exit beacon and shutdown will not be clean. michaeldo@chromium.org olivierrobin@chromium.org The thermal state of the device when a crash occured. Logged on application launch if the last session terminated in an unclean state. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. michaeldo@chromium.org olivierrobin@chromium.org Indicates whether or not one of the Stability.iOS.UTE.* metrics could explain the cause of the UTE which terminated the previous session. Logged on application launch if the last session terminated in an unclean state. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. justincohen@chromium.org olivierrobin@chromium.org Recorded when app starts after Unexplained Termination Event (UTE) or Explained Termination Event (XTE). Values other than Active indicate that prefs::kLastSessionExitedCleanly was not properly stored. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. michaeldo@chromium.org olivierrobin@chromium.org Recorded when app starts after Unexplained Termination Event (UTE) or Explained Termination Event (XTE). UTEs/XTEs can happen when app did not finish writing prefs. This histogram should help to understand if prefs did not get written during normal app termination sequence when ApplicationWillTerminate notification was called. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. olivierrobin@chromium.org sdefresne@chromium.org Recorded when app starts after Unexplained Termination Event (UTE) or Explained Termination Event (XTE). UTEs/XTEs can be caused by large memory allocations and this histogram provides information which memory heavy operation has being performed before UTE/XTE. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. olivierrobin@chromium.org michaeldo@chromium.org true if OS was restarted after the previous session. Logged on application launch if the last session terminated in an unclean state. If this is false then UTE was not caused by OS restart or shutdown. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. michaeldo@chromium.org olivierrobin@chromium.org Logged on the session following a crash with the result of a comparison between the OS version of the session which crashed and the current OS version. Logged on application launch if the last session terminated in an unclean state. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. michaeldo@chromium.org olivierrobin@chromium.org The estimated amount of time between when a crash occurred and when the user relaunched the application. Logged on application launch if the last session terminated in an unclean state. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. sangbaekpark@chromium.org media-dev-uma@chromium.org Recorded when a crash occurs in a CDM utility process. On crash, the exit code will indicate the exception code of the crash. sangbaekpark@chromium.org media-dev-uma@chromium.org Recorded when a CDM utility process either succeeded or failed to launch. sangbaekpark@chromium.org media-dev-uma@chromium.org A platform-specific error code returned from the attempt to launch a CDM utility process. Recorded when a CDM utility process fails to launch. sangbaekpark@chromium.org media-dev-uma@chromium.org An extended Windows error code returned from GetLastError when failing to launch a CDM utility process. Recorded when a utility process fails to launch on Windows. michaeldo@chromium.org olivierrobin@chromium.org Type of the shutdown. Prior to M146, this was recorded at startup and logs a sample for the previous session. Starting in M146, this is recorded at least 3 seconds after startup and attributed to the current session. Clean shutdowns are where the app enters the background before being killed. Other shutdowns are all some sort of crash. The absence of a crash log indicates that the app was killed by the OS, normally due to memory pressure. If memory pressure is extremely high, the app may not have had a chance to response to a memory warning before being killed. For first launch after upgrade discard this metric for unclear shutdowns, as the log is not recorded for the previous session. Prior to M146 this was also discarded, but recorded regardless of an unclear shutdown or not. Since this metric attributes the previous session's shutdown type to the current session's logs, configuration changes (e.g., OS version, Finch configurations) that might have affected the shutdown may not be correctly logged with the session they occurred in. fdoray@chromium.org catan-team@chromium.org Recorded when a renderer process exits abnormally. The value describes the type of content hosted by the renderer at the time of abnormal exit. fdoray@chromium.org catan-team@chromium.org Recorded when a renderer process hosting {HostedContentType} exits abnormally. The value describes the exit reason.