Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.2.5f1
Issue ID
1111639
Regression
No
There’s a significant pause before a first Debug.Log is executed after waiting for threads to complete
Repro steps:
1. Open user attached project
2. Enter Play Mode and press either one of the buttons in the Game View
3. Observe the messages in the Game View or in the Console
Notice that the time taken for the first Debug.Log message is significantly higher than for the second one
4. Repeat steps 2-3
Notice that now the time for both Debug.Log messages is similar
5. Exit Play Mode, open the LogAfterThreads script and uncomment the Debug.Log statement in the Start method
6. Repeat steps 2-3
Now the pause before the first Debug.Log call doesn’t occur
Reproducible with: 2017.4.18f1, 2018.2.20f1, 2018.3.2f1, 2019.1.0a13
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
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Resolution Note (2019.2.X):
This is not a bug. If you look at the profiler, you'll see that the increased time is spent in Mono JIT.