I just recently opened up a new project and was immediately hit with an abnormally high crash rate. In all fairness, on release there WAS an actual crashing issue. I fixed it pretty quickly, and watched the crash stat drop enormously. Then a really strange behavior emerged. My crash stat went from 70-80% total, to 30-40% total, but the individual platform crashes dropped to zero:
I then spent the next few days on absolute optimization overdrive. I was able to cut this total down from 40% to 8% and was very proud of myself, but still really concerned and frustrated because 8% is still crazy high. This behavior of 0% on all platforms, but a high total stat continued.
Due to this high rate, we decided to private the game and close it down for private testing until we could find the issue. During these private testing sessions, we did find the issue. The Crash Rate stat is completely wrong, it reports a crash everytime a user closes the app on their phone, or closes the Roblox window on PC. Which are very common ways to exit a game, especially one in our genre. Not a single one of our testers experienced a crash during this period:
This is obviously quite concerning, because I think these crash stats might contribute to the game’s performance in the algorithm. It certainly contributed to our decision to completely close the game. It also means that games with certain audiences like ours are more likely to over-report crashes than others. People alt-f4 from our game all the time, it’s a shooter with a majority 17+ audience.
Hi @CDDevelopment ,
What game has this specific problem? If you could share with me the link to the place or just a place id, I could pull some internal data for investigation.
I also noticed that after your fix the crash rate of computer dropped to zero, but total remains high, which means the rest of the crashes probably all come from mobile platforms. Is that right?
I’m inclined to say no, I don’t think the crashes are from mobile. There are periods of time in which there are actual crashes/disconnects from mobile or tablet and those appear as attributed to the proper platform. In our testing sessions, the total number appeared at 100% when any user, on any platform, exited the game normally by closing the app.
This same bug of appearing as crashes does occur on other games in our group as well, but this game in particular seems more affected by it than the others.
9/20/23 6pm - 9/21/23 4am (I think this is in EST because I’m EST)
^ This is after the last major optimization and before we privated the game. Lots of instances where crash rate is little to nothing on all platforms, but total is up at 25%.
9/21/23 11am - 9/21/23 9pm
^ this is after we privated the game and opened it up to a small group of testers. Lots of 100% crash rates, no platform specific crashes reported, and not a single one of our testers actually experienced a crash.
I think it might be some kind of issue with this particular game’s analytics. Like maybe launching the game with a crashing issue has permanently poisoned our crash rate stat? I published a version with 0 scripts and tested it, crash rate still reported at 100%. So we know it’s not anything on our end causing the crash reports to be inaccurate.
Hi: Is this still an issue? I am checking your experience and the crash rate is around 1%, which seems quite good. Let us know if you still observe some issues. Thanks!
This issue isn’t quite fixed. I fixed alot of other performance related problems that were causing crashes which is how I got the crash rate this low. However, in private testing we can still see that users exiting games normally does still contribute to the crash rate.
Also as part of my optimization work, I bought the oldest, worst tablet I could find. It plays the game at 15 FPS, but I was still unable to trigger a crash at all.
