Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a3
2019.1.0a1
2019.2.0a1
Issue ID
1117209
Regression
Yes
The time of exit from Play mode increased several times when using newer Unity version
How to reproduce:
1. Open attached "playmode.zip" project
2. Click Play mode button to go into Play Mode
3. Click Play mode button to go into Edit Mode
4. Observe console
Expected result: Exit time is similar in all versions
Actual result: Exit time increased several times in newer Unity versions
Reproducible: 2018.3.3f1, 2019.1.0a14, 2019.2.0a1
Not reproducible: 2017.3.0a1, 2017.4.18f1, 2018.2.0a1, 2018.2.20f1, 2018.3.0a2
Partial workaround: Under the Configuration section of the Player Settings, select "Disable HW Statistics".
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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Resolution Note (fix version 2018.3):
Fixed in: 2019.2.0a9
Backported to: 2018.3.12f1, 2019.1.0b9