> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Browser Crash Monitoring

> GermainUX RUM Extension monitors supported browser crash events and creates a KPI fact when a browser, tab, GPU process, or extension crashes or reloads.

Components
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)
[`RUM Extension`](https://docs.germainux.com/main/germain-ux-rum-extension)

Availability
2026.1 or later

Browser support
only latest Chrome, Edge and Opera

> **[Benefits](#benefits)**
>
> Advantages of crash alerts

> **[Configure the threshold](#configure-the-threshold)**
>
> Set crash count alert level

> **[Limitations](#limitations)**
>
> What crash detection misses

> **[Deployment and configuration](#deployment-and-configuration)**
>
> Install and tune crash monitoring

## Overview

GermainUX RUM Extension monitors supported browser crash events and creates a KPI fact when a browser, tab, GPU process, or extension crashes, or when the browser forces a reload.

Browser Crash Monitoring helps teams identify unstable browser experiences, determine which users and applications were affected, and correlate crashes with activity recorded before the interruption.

## Benefits

Browser Crash Monitoring helps organizations:

* Detect supported browser and tab crashes in real time.
* Identify affected users, applications, pages, and browser versions.
* Distinguish browser crashes from JavaScript errors or browser freezes.
* Analyze crash frequency and trends.
* Identify crashes concentrated within a specific application version, browser, device, or workflow.
* Review available user and technical activity preceding the crash.
* Notify interested GermainUX users when a crash is detected.
* Prioritize issues according to affected users and business impact.

## Preconfigured monitoring

Browser Crash Monitoring is available through the GermainUX RUM Extension.

GermainUX supports the following crash-event categories when they are exposed by the browser:

| Crash type | Description |
| - | - |
| Full Crash | The browser terminates unexpectedly |
| Tab Crash | A browser tab crashes, such as Chrome’s **Aw, Snap!** condition |
| GPU Crash | The browser’s graphics-processing component crashes |
| Extension Crash | A monitored browser extension crashes |
| Forced Reload | The browser reloads a page because of a mobile, memory, or similar browser condition |

The precise event details depend on what the browser and extension-management APIs make available.

## What GermainUX records

A browser crash event can include available context such as:

* Crash type
* Event timestamp
* Application
* Page or URL
* Environment
* Browser and browser version

> **Show all 11**
>
> * Operating system
> * User or session identifier, when authorized
> * Extension identifier, when relevant
> * Related user-session activity
> * Available technical events preceding the crash

Not every crash provides the same information. A sudden browser or operating-system termination can prevent the browser from transmitting its final state.

## Browser crash versus other browser issues

Browser Crash Monitoring should not be used as a general category for every browser-side failure.

| Condition | GermainUX monitoring |
| - | - |
| Browser, tab, GPU, or extension terminates | Browser Crash Monitoring |
| Page becomes temporarily unresponsive | JavaScript Long Task or Browser Freeze Monitoring |
| JavaScript code throws an exception | JavaScript Console and Error Monitoring |
| A promise fails without being handled | Unhandled Promise Rejection Monitoring |
| An HTTP request fails | Network Requests Monitoring |
| A user clicks an ineffective element | Dead or Error Click Monitoring |
| Page memory increases abnormally | JavaScript and Page Memory Monitoring |

Analyzing these KPIs together helps determine whether a crash was preceded by high memory consumption, long-running JavaScript, application errors, or another observable condition.

## Enable Browser Crash Monitoring

Browser Crash Monitoring requires the [GermainUX RUM Extension](https://docs.germainux.com/main/germain-ux-rum-extension.md).

### Enable steps

1. Sign in to the GermainUX Workspace.
2. Go to **Settings > Germain State > Browser Extensions**.
3. Select the browser-extension application.
4. Locate **Crash Monitoring**.

   ![Browser Crash Monitoring: Enable steps](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/browser-crash-monitoring/image-20260424-195707.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=1f5aaedb238414f3eb4371034eb745f8)
5. Enable the setting.
6. Save the configuration.
7. Refresh or restart the extension when required.
8. Confirm that the updated configuration reaches the monitored browsers.

Workspace labels can vary by GermainUX version.

## Configure the threshold

GermainUX can create an insight when the number of detected browser crashes reaches the configured threshold.

The following example sets the threshold to one crash:

```javascript theme={null}
const settings = germainApm.getDefaultSettings();

settings.plugins.browsercrash.levelThreshold = 1;

germainApm.start(settings);
```

A value of `1` means that the first supported crash occurrence meets the configured threshold.

Customize this value only when the default behavior does not meet the organization’s requirements.

## KPIs and analysis

Use the browser crash KPI to analyze:

* Crash count
* Unique users affected
* Unique sessions affected
* Crash rate
* Crash type
* Browser and browser version

> **Show all 11**
>
> * Operating system
> * Application and environment
> * Page or URL
> * Application version
> * Time period

Useful analytical questions include:

* Which application or page experiences the most crashes?
* Did crashes increase after a release?
* Are crashes concentrated in one browser version?
* How many users and sessions were affected?
* Are GPU crashes limited to particular devices?
* Did memory usage, long tasks, or JavaScript errors increase before the crashes?
* Which workflows were interrupted?

Review the available KPIs for Browser Monitoring.

## Correlation with user activity

When compatible browser and session telemetry is available, GermainUX can correlate a crash with:

* The affected user session
* Page navigation
* User interactions
* JavaScript errors
* Unhandled promise rejections
* Browser memory

> **Show all 10**
>
> * JavaScript long tasks
> * Network requests
> * Application version
> * Business-process milestones

The activity captured before the crash can help identify contributing conditions. It does not necessarily prove that a particular event caused the crash.

Session Replay ends at the last activity successfully transmitted before the browser or tab stopped functioning. The crash itself cannot be visually recorded after the browser context has terminated.

## Notifications

A browser crash insight can be used to:

* Trigger an alert when an SLA is violated.
* Notify interested GermainUX users through a Watch.
* Appear in a dashboard or report.
* Initiate an approved diagnostic workflow.
* Create a ticket through an authorized integration.

For example, a Watch can notify a support engineer whenever GermainUX detects a tab crash for a critical application.

A Watch applies a notification to the crash insight already detected by GermainUX; it does not create a new crash insight.

## Limitations

Browser Crash Monitoring is subject to browser and extension API limitations.

GermainUX may be unable to detect or fully describe:

* A computer losing power
* An operating-system crash
* A browser process terminated by the operating system
* A browser removed before the event is transmitted
* A network loss that prevents the crash event from reaching GermainUX
* Crashes not exposed through the browser’s extension APIs
* Crashes occurring outside the authorized monitored browser
* Application failures that do not cause the browser or tab to crash

A missing crash event does not prove that the browser remained operational.

## Security and privacy

Browser crash facts generally contain technical metadata, but related sessions can include user and business information.

Before production deployment:

* Confirm which applications and users may be monitored.
* Mask or exclude sensitive Session Replay content.
* Restrict access to individual user and crash details.
* Avoid collecting unnecessary URLs or identifiers.
* Configure retention and deletion requirements.
* Ensure that centrally deployed extensions follow organizational policy.
* Inform monitored users when required by the organization’s compliance program.

## Validation

Browser crashes should not normally be forced on production users. Validate the configuration in a controlled test environment.

1. Install and the RUM Extension in a supported test browser.
2. Confirm that the browser-extension application appears in GermainUX.
3. Enable **Crash Monitoring**.
4. Confirm that the extension receives the updated configuration.
5. Reproduce a supported test crash using an approved method.
6. Confirm that a Browser Crash fact appears in GermainUX.

   ![Browser Crash Monitoring: Validation](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/browser-crash-monitoring/image-20260411-152734.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=38657d1bacc8ddbb6dbd67ea2486654e)
7. Verify the crash type, browser, application, page, and timestamp.
8. Confirm that the event is associated with the appropriate session when possible.
9. Test the configured SLA, alert, or Watch.
10. Confirm that monitoring resumes after the browser or tab restarts.

## Troubleshooting

If crash events are not collected:

1. Confirm that the GermainUX RUM Extension is installed and enabled.
2. Verify that **Crash Monitoring** is enabled for the application.
3. Confirm that the extension received its latest configuration.
4. Verify that the browser and version support the required extension APIs.
5. Confirm that the application URL matches the configured monitoring scope.
6. Verify that the browser can connect to GermainUX.
7. Check browser and extension policies.
8. Confirm that another extension or endpoint-security product is not blocking GermainUX.
9. Review available browser-extension and GermainUX logs.
10. Confirm that the tested condition is a supported browser crash rather than a JavaScript error or freeze.

## Deployment and configuration

* Deploy the [GermainUX RUM Extension](https://docs.germainux.com/main/germain-ux-rum-extension.md).
* Create or select the browser-extension application and UX Monitoring Profile.
* Enable **Crash Monitoring** under **Settings > Germain State > Browser Extensions**.
* Use the preconfigured crash threshold or customize it when required.
* Review the available Browser Monitoring KPIs.
* Correlate crashes with Session Replay, memory, JavaScript, network, and long-task insights.
* Configure SLAs, alerts, Watches, dashboards, and reports when required.
* Validate crash detection safely in a controlled environment before production rollout.

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.