Search Issue Tracker
Active
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warning says instancing will be disabled when used with static batching but it is still working and breaking result object color
- GL viewport is wrongly scaled when there's a camera which has a partial viewport
- [TestRunner] NUnit tests doesn't time out when [Timeout()] attribute is set
- When "draw instanced" is changed for entire terrain group and then undone, it is only undone for the terrain that was selected
- Custom Inspectors OnDisable still called after Asset has been deleted
Add comment