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.
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.
To enable Crash reports all we have to do is add a new HTTP response header.
The setup above will tell browsers to send Crash reports to Flowports, so you can take proactive actions to prevent them from happening again.