Search Issue Tracker
Not Reproducible
Votes
1
Found in
5.2.0p1
Issue ID
728877
Regression
Yes
[Atomics] Device freezes in an apparent loop after running project for a while or at startup
How to reproduce:
1. Open attached project
2. Build to iOS and run
3. Play the game for a while
- The game freezes, but Xcode does not react as if the project crashed
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Woody4618
Oct 31, 2015 11:29
Hey, I think i tracked it down to Canvas.RenderOverlays wait for Job Canvas.sort. That was also what i saw where it hang in Xcode.
It is easily reproducable.
Create a Canvas with a canvas scaler, scale with screen size. Add a scroll view and add a view elements. Set the reference resolution high. Its very easily seeable with high values, like 80000 or something. Then deploy to mobile, scroll the view and watch the profiler.
The sort job takes about 60 ms per frame. I guess the egine is then waiting for it or triggers it again when its not yet done and then it loops forever. I guess its related to putting the sorting into a seperate thread. http://blogs.unity3d.com/2015/09/07/making-the-ui-backend-faster/
Took me two days to figure out that it is probably a unity bug :(