An application starts hanging intermittently, scrolling is not smooth as it was before, the browser becomes unresponsive and then it finally crashes. We've all had that experience at least once and it's one of web administrators' worse nightmare to know their web apps are causing browsers to crash.

There are a lot of error logging methods and libraries out there that can be used to intercept errors in JavaScript and store them, but when the browsers crashes, how do we get that from JavaScript? You don't. At that stage, the page is unresponsive and is unable to process anything else.

If we don't know when and why it crashes, how do we fix it? Thanks to a new Reporting API specification from the W3C, browsers are now able to send Crash reports to a server alongside the reason.

Does your website have Crash reports enabled? Check it now.

Practical Example

To enable Crash reports all we have to do is add a new HTTP response header.

Report-To: {"group":"default","endpoints":[{"url":""}],"max_age":86400,"include_subdomains":true}
Reporting-Endpoints: default=""

The setup above will tell browsers to send Crash reports to Flowports, so you can take proactive actions to prevent them from happening again.

Crash Screenshot
An example of a Crash report collected by Flowports.
We can be your report collector so you don't need to build your own. Sign up for a free trial of Flowports to get started.Try it free now!