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
- Text Object position shifts when selecting multiple Text Objects and expanding the Extra Settings in the Inspector
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
This is a duplicate of issue #918779