Bug Unity build getting freezes or FPS getting 0 in between running game.

Hello Unity folks!
I am experiencing a very frustrating thing recently in my Unity game. My games are working fine on Unity version 2020.3.22f1. There was no any issue on that. Now I have upgraded my Unity version to LTS 2022.3.7f1. And now my Unity release build is getting stuck/frozen or lagging to much, FPS goes almost to 0 I think. This is also not happening always. Occurring sometimes for some users. Unable to play, move anything. In that case user has only one option to quit the app and start again. Never happens on Editor only in release builds. So unable to debug this as well. Unable to understand whats happening. I have also attached a screenshot. In this game was working fine and its just got stuck there. nothing happens after that. you have to quit the app there.
Solution I have already try is disable the "Optimized Frame Pacing" but this did help me. I have been stuck or finding the solution for this for weeks. Please help me guys if anyone have the solution for this. Thanks a lot in advance!

 

Start all performance investigations with the profiler. Find out what is dogging your app down.

In the case you describe above, my first random guess is that you are doing too much in FixedUpdate().

This mistake can have an interesting sudden performance cliff appearance, where everything is fine and suddenly it drops down to 5 fps when you break that barrier of what can be safely done in the FixedUpdate() time window.

Do absolutely NOTHING in FixedUpdate() if possible, and when you must use FixedUpdate(), be sure it is 100% solely for transacting against the Physics or Physics2D engine and absolutely nothing else.



Here is some timing diagram help:

https://docs.unity3d.com/Manual/ExecutionOrder.html



Two good discussions on Update() vs FixedUpdate() timing:

https://jacksondunstan.com/articles/4824

https://johnaustin.io/articles/2019/fix-your-unity-timestep




DO NOT OPTIMIZE "JUST BECAUSE..." If you don't have a problem, DO NOT OPTIMIZE!

If you DO have a problem, there is only ONE way to find out. Always start by using the profiler:

Window -> Analysis -> Profiler

Failure to use the profiler first means you're just guessing, making a mess of your code for no good reason.

Not only that but performance on platform A will likely be completely different than platform B. Test on the platform(s) that you care about, and test to the extent that it is worth your effort, and no more.

https://forum.unity.com/threads/is-...ng-square-roots-in-2021.1111063/#post-7148770

Remember that you are gathering information at this stage. You cannot FIX until you FIND.

Remember that optimized code is ALWAYS harder to work with and more brittle, making subsequent feature development difficult or impossible, or incurring massive technical debt on future development.

Don't forget about the Frame Debugger either, available right near the Profiler in the menu system.

Notes on optimizing UnityEngine.UI setups:

https://forum.unity.com/threads/how...form-data-into-an-array.1134520/#post-7289413

At a minimum you want to clearly understand what performance issues you are having:

- running too slowly?
- loading too slowly?
- using too much runtime memory?
- final bundle too large?
- too much network traffic?
- something else?

If you are unable to engage the profiler, then your next solution is gross guessing changes, such as "reimport all textures as 32x32 tiny textures" or "replace some complex 3D objects with cubes/capsules" to try and figure out what is bogging you down.

Each experiment you do may give you intel about what is causing the performance issue that you identified. More importantly let you eliminate candidates for optimization. For instance if you swap out your biggest textures with 32x32 stamps and you STILL have a problem, you may be able to eliminate textures as an issue and move onto something else.

This sort of speculative optimization assumes you're properly using source control so it takes one click to revert to the way your project was before if there is no improvement, while carefully making notes about what you have tried and more importantly what results it has had.

"Software does not run in a magic fairy aether powered by the fevered dreams of CS PhDs." - Mike Acton

 

@Kurt-Dekker Thanks for reply and some useful suggestions but I have a doubt that its not happening in my any single game. Its happening across my all games, its either 2D game or 3D which were working fine on the previous version of Unity. Some 2D games where not a single FixedUpdate() has been used and not high graphics rich UI/UX.
Is there any Editor settings like "Optimized frame pacing" enable/disable which I am missing that causing this issue. Please let me know.
Thanks!

 

hi @MartinTilo Thanks for the replay. Actually I have upgraded from Editor version 2020.3.22f1 to 2022.2.1f1 firstly and then within a week shifted to 2022.3.7f1 which is the LTS version.
Yes, correct looks like the same issue as you have mentioned in the other thread. So what is the solution for this. Do we have any fix for this as of now? My all apps are down and do not what to do next. Please please please help me with this.
Thanks!

 

hi @MartinTilo I think, I have the reproduction steps and its mostly related to memory leak. Initially I was not able to reproduce this but yesterday I got this issue on staging build as well. I had played a single game continuously for quite a long time like almost 15-20 mints and then in between game got stuck. I have tried this multiple times and every time I was able to reproduce that. No logs, No ANR, No Crash etc nothing just game got stuck/freeze.

 

You can check the video attached.

 

Sure, I will do that, but can you let me know which option I should pick here and also tell me about other details so that it will more effective. Please check the screenshot attached.
Thanks!

 

@MartinTilo is it the same issue as mentioned on this thread. As @TwoYen and you also have mentioned here that it has been fixed in Unity version 2203.10f1. please confirm.
Thanks!