You can use our filters to find the UI Freeze problems.
This will indicate when the app is frozen or stuck during the user interaction. It’s important to detect and diagnose these issues as they can cause frustration for your users.
To find all the UI Freezes, just go to Sessions, click on the filters and select UI Freeze under Events:
You can also search for additional properties such as a specific screen or the UI Freeze duration:
Once you play the Session where the UI Freeze event occurred, you can see the UI Freeze log and easily copy it to share it with your developers. What’s more, if you take a look at the session replay, you can see exactly in which screen it happened and how the user reacted to that.
What’s the difference between Crash and UI Freeze
A crash occurs when there’s an unexpected exit caused by an exception or signal that has not been addressed during development. When an unexpected signal occurs, the app will crash and be forced to close.
The UI Freeze happens when you run a process on the UI thread that takes too long and it can’t process the user input. In such cases, the app will be blocked or frozen and will not necessarily be forced closed.
We detect UI Freeze's by adding a piece of code that tries to run on the main thread at regular intervals. If the gap between runs is unexpectedly high we declare an UI Freeze, and capture stack details at that point