What causes an unprioritized list of crashes?

Without a measure of player impact, crashes are prioritized by recency or who shouted loudest, so effort goes to low-impact bugs while the ones hurting the most players linger.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Use Crash-Free Rate to Prioritize Bug Fixes

Quick answer: Measure the crash-free session and user rate, rank crash signatures by how much each lowers it, and fix the ones costing the most players first.

Crash-free rate turns a crash list into a priority order by player impact. Here is how to use it.

How to fix it

1. Measure crash-free sessions and users

Track the percentage of sessions and unique users that experience no crash. This is the headline health metric, and it tells you how much room there is to improve and whether you are improving.

2. Rank signatures by impact

Attribute the drop in crash-free rate to each crash signature — how many unique users it hits. Rank by that, not raw event count, so you see which crashes actually move the metric.

3. Fix the highest-impact first

Work down the ranked list, fixing the crash that affects the most users first. Each fix raises the crash-free rate the most for the least effort, and you can watch the metric improve per release.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.