So I’m trying to diagnose a crashing issue in my game, and I’m using the crash rate stat somewhat effectively to narrow down causes.
One issue however, is that the crash report changes retroactively, without explanation.
At 2:10, the crash report was 0% for the time between 1:16 and 1:28. Super great, provided me with what felt like some good information.
Fast forward 10 minutes later, refreshed the page, and now the crash rate for those SAME EXACT TIMES reports that it was as high as 3%.
If it takes 1 hour for the stats of “The Past Hour” to report correctly, it makes the entire concept of hourly reporting completely useless.
3 Likes
Here’s a video of it happening:
Now it can’t decide what the crash rate was at all:
Hi:
Thanks for reporting the issue. There are some issue with the crash rate right now and we are trying to fix.
Meanwhile, one more thing we need to point out is that the crash on Roblox is a little bit different. Since Roblox is not an operating system, if the crash happens and the app is killed, the information cannot be reported back to our system until the user reopens the app. It could cause that our system records a crash after some time. So the historical crash rate could change since we want to attribute the crash to the correct time stamp. Therefore you might see the crash rate for the past hour keeps changing. We are working with our product to provide better information on the chart (for example, dotted line to indicate it is an estimate or projected value) so people won’t get confused when the rate changes.
Let us know if you have any other suggestions. Thanks!
1 Like
I would really love if the log files from crashed clients were circulated to developers automatically in some way. Not a single one of my hundreds of community testers can trigger a crash on any of their devices and yet there’s still a reported 10% crash rate. This has left me completely in the dark as to what the cause is.
Furthermore even if I could get into contact with any of the users experiencing a crash, unless they’re on PC they can’t send me a log file regardless.
Hi:
We have improved our report for crash rate. However, this change will still appear because the report for crashes takes time for games and we want to reflect the most accurate crash rate based on when the crash happens so it is possible when you come back and look at the crash rate, some historical data points change the value.
We decide to use this way instead of using the report time of crashes because you might have updates in between and the report time might give you the wrong idea that the crash is due to the newest update.
This is something we cannot easily change since crash could only be reported after the app is restarted and there is no guarantee when that will happen from client side. We hope you understand this techinical limitation. We will update the documentation to make it more clear on what the crash rate mean and how it is recorded and computed. Thanks!
