Search Issue Tracker
Duplicate
Votes
2
Found in
2018.4
2019.3.2f1
2020.2
Issue ID
1223699
Regression
No
[Linux] Entering Play Mode causes the Editor to freeze when there are above a hundred Sprite Renderers and Animators in Scene
Reproduction steps:
1. Import the attached Package to an empty project (Freeze.unitypackage)
2. Open the 'BingGoal' Scene (Assets/Game/BingoGoal/Scenes/BingoGoal)
3. Enter Play Mode
Expected result: It takes a second or so to enter Play Mode
Actual result: The Editor freezes for some time before entering Play Mode
Reproducible with: 2018.4.21f1, 2019.3.10f1, 2020.1.0b5, 2020.2.0a7
Not reproducible with: 2017.4.39f1
Notes:
- Not reproducible on Windows and macOS
- It takes ~30 seconds to enter Play Mode in 2018.4.21f1, ~1 minute in 2019.3.10f1 and ~1.3 minutes with newer versions
- There are around 112 GameObjects with Animator and 140 GameObjects with Sprite Renderer in this Scene
-
Resolution Note (2020.2.X):
This is resolved in 2020.2.0a8, 2020.1.0b8 and 2019.3.10f1.
Comments (1)
-
wenderRondonia
Apr 20, 2020 11:20
waiting vigorously for the fix 0.0
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
- Error ‘cannot use casts on l-values’ when a variable is assigned inside a second-level nested if statement before being used in a conversion
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
This is a duplicate of issue #918779