Crash Reporting


Debug JavaScript in Firefox in 7 easy steps

This article will focus on debugging JavaScript code within Firefox’s Developer Tools. The Dev Tools within Firefox are extremely powerful which will speed up finding and fixing bugs. We’ll be using Raygun Crash Reporting to find the stack trace and the line of code the error occurred on. You can sign up for a free 14-day trial here. So, let’s dive in!


New Feature: Number of Users Affected by a Crash

We've just released a way to track the number of users affected by a crash! If you navigate to the Summary page, you'll now see a column labeled 'Users Affected’, this column shows how many unique users have been affected for each row in the crash summary table. With the data provided by this new column, you’ll have additional information available for prioritizing fixes. The ‘Count’ column is unchanged, and reports the total number of crashes reported by all users.


Robust JavaScript Error Handling. Learn About JavaScript Errors

By combining custom errors, named functions and Bugfender, you can create a robust error-handling process that allows you to immediately identify the defects of your JavaScript apps. Unhandled JavaScript errors will stop the execution of your script, leaving the application in an undesired state – or, even worse, in an unknown state. So you need a robust error-handling process to avoid unknown errors in your apps. But, why are errors thrown anyway?


The Great Irony of Serverless Computing

Working with Serverless computing is like riding an electric bike. You get speed, flexibility, automatic assistance to scale with ease. Development is usually hassle-free because you can focus on code and only pay for usage of the service. Except when your users hit an error. Debugging that issue feels like your bike’s battery just died while climbing a steep hill.


How we scale Raygun's architecture to handle more data

Due to the huge importance of sourcemaps in the workflow of our customers, sourcemaps are a crucial part of our Crash Reporting offering. We constantly strive to stay ahead of our customer demands as the amount of data we process continues to grow. We identified the sourcemapping process as an area ripe for performance improvement, so we took it apart and looked at exciting ways to build it from the ground-up using cutting-edge tech.


Support for Crashpad Attachments

BugSplat now supports attachments for Crashpad out of the box. Developers can include additional files with the Crashpad crash upload using the newest release of the BugSplat Crashpad SDK. This release includes updated examples that show how to include Crashpad attachments for Windows, Linux, Android, Qt Windows, and Qt Linux (but not yet for macOS). Before this change, including attachments with Crashpad out of the box was difficult.


Introducing Android Crash Reporting with BugSplat

BugSplat users can now collect Android crashes with the Crashpad SDK. If you're supporting a cross-platform C++ application, porting a C++ application to Android, or creating a new NDK library from scratch, you can now use BugSplat to track, collect, and debug your Android crashes. This will bring the same in-depth view of crash events you get with BugSplat on other languages to your Android application.


Never miss another crash! Instana's Crash Detector brings real-time Abnormal Process Termination analysis to Linux

Irrespective of how many levels of abstraction are constantly being introduced like containers and serverless, your code is run by the operating system in processes. And those processes can and will encounter issues, causing them to exit with erroneous status codes. In other cases, the operating system or something else running on it, will kill your processes, or send them other signals that will cause them to shut down.


Make sense of application issues with Datadog Error Tracking

When your applications raise errors, you need a way to make sense of them so you can set priorities, start troubleshooting, and gauge the success of your efforts. Errors can appear within the thousands of browser sessions and backend hosts running your software, making it difficult to find meaning within the noise. This is especially true of frontend errors, where seemingly endless permutations of browser version, location, and other environmental details can make it hard to spot trends.