Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
2
Found in
2019.1
2019.3
2019.3.0a5
Issue ID
1161373
Regression
Yes
2019.3 and 2019.1 Unity versions are significantly slower when entering the play mode
How I tested this:
1. Created empty project
2. Added scripts for testing (attached below)
3. Entered and exited the play mode 5 times
4. Recorded data
Results when compared to the best performing (out of supported version) 2017.4.29f1:
- 2019.3.0a7 is 80%-100% slower
- 2019.2.0b7 is only ~18% slower (notice that 2019.2.0a1 was 71% slower)
- 2019.1.8f1 is 50% -80% slower
- 2018.4.3f1 is ~ 40% slower
- 2017.4.29f1 is a baseline
- 2017.2.5f1 is 10- 15% slower
Note:
- Tested on two different Windows 10 machines
Comments (1)
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Peter77
Jun 21, 2019 15:28
Related forum thread:
https://forum.unity.com/threads/case-1161373-2019-3-enter-playmode-time-significantly-increased.692005/