How do I calculate crash-free rate?
Crash-free sessions = 1 minus (sessions with a crash / all sessions). Crash-free players = 1 minus (players with a crash / all players). In Manalens, a crash is an app_unclean_exit event or an unhandled critical error. Compare builds over the same number of days, because a longer range has more sessions for each player.
Sources: Manalens error tracking documentation.
What is a worked example?
Example numbers: build 572 has 20,000 sessions from 4,000 players. 300 sessions end in a crash, from 240 players. Crash-free sessions are 1 minus 300 / 20,000 = 98.5%. Crash-free players are 1 minus 240 / 4,000 = 94%. The player rate is lower, because one crash spoils a whole player.
Sources: worked example.
Why does crash-free rate matter for indie PC and web games?
PC games run on many GPUs, drivers and operating systems, so a build that is fine on your machine can crash for some players. A crash in the first two hours is a direct refund risk on Steam. Valve gives a refund for any reason within 14 days of purchase if the player played less than two hours. Watch the crash-free rate of each new build in its first days.
Sources: Steam Refunds policy.
How do I measure crash-free rate in Manalens?
Create a board from the Game health template. It shows crash-free sessions and crash-free players, errors per session by build, and a Top errors table. The Godot and Unity SDKs send app_unclean_exit at the next launch when the last run did not exit normally while the game had focus. Manalens does not store native crash dumps or symbols.
- Game crash analytics: link crashes to refunds and bad reviews →
- Best crash reporting tools for indie games in 2026 →
- Custom dashboards →
- Game tracking plan generator →
Sources: Manalens error tracking documentation.
Frequently asked questions
What counts as a crash in Manalens?
An app_unclean_exit event, sent at the next launch when the last run did not exit normally while the game had focus, or an error with severity critical and handled false. A normal quit does not count. A game that the operating system closed in the background does not count either.
Should I track crash-free sessions or crash-free players?
Both. The session rate shows how often the game crashes. The player rate shows how many people had a bad time, and it is usually lower. In the example on this page, crash-free sessions are 98.5% but crash-free players are 94%.
Do I still need a crash reporter?
For native crashes, yes. Manalens counts crashes with app_unclean_exit, but it does not store native crash dumps or symbols. For a segfault in the engine or a native extension, keep a tool such as Sentry or Backtrace for the dump.