Crash rate measures the percentage of plays of your Playable that ended in a crash. Each crashed play is counted under one reason, so the reasons add up to your total crash rate.
| Crash reason | What it means | Common fixes |
|---|---|---|
| Webview crash during play | The webview hosting your Playable crashed unexpectedly during gameplay. | This most commonly happens due to exceeding the JavaScript Memory limit on iOS (512 MB). Reduce peak memory usage during gameplay by loading assets only when needed, freeing up unused assets and objects, and using smaller media files. |
| Webview crash before start | The webview hosting your Playable crashed unexpectedly before gameplay. | This most commonly happens due to exceeding the JavaScript Memory limit on iOS (512 MB). Load fewer assets up front, or load them later. |
| App crash | The YouTube app closed unexpectedly, for a reason other than memory. | Check if crash increases line up with a shipped Playables update, and check for devices with the most crashes. |
| App stall | The YouTube app froze and stopped responding. | Split long-running tasks into smaller pieces. |
| App out of memory | The device ran out of memory and closed the YouTube app. | Reduce total memory use. |