Finding Your Most Critical Defects

And fixing your most frequent crashes

Share:

Getting detailed and accurate crash data is essential for finding critical defects, but most applications have more defects than can be fixed. How do you evaluate if a bug is significant enough to fix?

Sometimes the answer is obvious—the content of the crash shows how significant the defect is, the fix is obvious, and fixing the defect is cheaper and easier than living with it.

This isn't the case for many bugs and their severity should often be tied to how often they're happening, and how many users are seeing them.

For this reason, BugSplat groups similar crashes together and shows you the most frequently occuring groups on the Summary page. This gives you a powerful tool to evaluate defects based on how frequently they are causing crashes for your users.

Visibility into crash frequency

When determining which defects to prioritize first, it's handy to know how frequently each crash is happening. With this information, you can identify the bugs that have the most substantial impact on making your app more stable.

1,000-foot view


To get an overview of the defects causing the most crashes in your application, navigate to the Summary page.

BugSplat Crash Report Main

The Summary page groups similar crashes together, and by default orders these groups starting with the most frequent crash. Each group is labeled with a Stack Key, which is the function name, source file, and line number in the call stack.

By default, crashes are grouped using the top level of the call stack, and therefore the Stack Key shown corresponds to the top level of a call stack. You can group crash reports at a different level of the call stack. See our Sub Key feature for the details.

View your Application or Version

BugSplat Crash Report Main

The Summary page gives you the ability to filter your crash data by Database, Application, or by Version. These controls are global, and will affect all pages that display crash data. Are you only interested in your most recent releases? It's easy to specify a subset of versions to display using the Version filter. And, this filter will stay active between pages.

In addition, you can get specify any time frame to search using the Timespan dropdown control.

Chart you Stack Keys

Useful for visualizing how your crashes vary over time—the charting tool will help you understand when crashes are occurring and if your fixes have been effective. Select the lefthand checkbox of any row to add it to the chart.

Sort your Stack Keys

BugSplat Crash Report Main

This grid shows you your top Stack Keys sorted by Count. Select the checkbox on the left to chart them in the Stack Key Overview or hit the carrot to view more data on each Stack Key individually.

Click the link to see more details on each Stack Key (more on this in a second)

Column Search

BugSplat Crash Report Main

Finally, you can find a specific group of crashes by using the Column Search tool to filter out Stack Keys that don't match your query.

Inside the Stack Key


BugSplat Crash Report Main

To further explore a group of crashes, you can select any Stack Key to navigate to the Key Crash page, which displays all of the individual crashes that are in the Stack Key.

Finding Crashes from a Specific Time Frame

BugSplat Crash Report Main

Inside of the Key Crash page, you can quickly sort the crashes by a specific time frame to find particular examples of crashes that were caused by this crash defect.

Charting Crashes Inside of a Stack Key

BugSplat Crash Report Main

Using Key Crash charting, you can answer a lot of critical questions helpful for prioritizing and fixing a defect. Questions include: Are crashes becoming more or less frequent for this crash defect? When did the first crash of this kind occur? When was the last crash to occur?

Collaborative Tools

BugSplat Crash Report Main

Add a comment for your team about the defect or create an issue in your defect tracking tool using the controls in this area.

The Tech Support Response button configures a message to be displayed to your users after they have submitted a crash report. This message will only be shown to users submitting new crashes with this particular Stack Key.

This lets your customer know that their crash has been seen before and gives your team the ability to tell them more about the problem.

The Call Stack Explorer allows you to view all the call stacks associated with a single Stack Key in a tree control.

Select individual crashes for more info

BugSplat Crash Report Main

Select any of the individual crashes additional details to learn more about the crash.

Select the row expander control on the left to quickly view more information about the crash, or select the crash id link to navigate to the crash details page.

Filter and sort to find specific crash examples

BugSplat Crash Report Main

Use the Column Search tool to filter out unwanted crashes or find a specific crash or crash set that will help you evaluate and fix the defect. Sort by selecting any column header.

BugSplat 101

Check out our other guides for getting you up and deployed with BugSplatf

Sign up for BugSplat

30-day trial. No credit card needed.