Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
3
Found in
2017.3.1p1
Issue ID
1033280
Regression
No
[Profiler] Incorrect processes are assigned to coroutines in CoroutinesDelayedCalls when in Play mode
To reproduce:
1. Open user's attached project "CoroutineTest.zip", scene "test"
2. Make sure Profiler window is visible and VSync graph under CPU Usage is hidden (for better visibility)
3. Enter Play mode and observe Profiler until spike in scripting happens (several seconds)
4. Select the frame which spiked and check it's Coroutines' activity in Overview (Update.ScriptRunDelayedDynamicFrameRate/CoroutinesDelayedCalls)
Expected: activity is assigned to correct coroutines (A.ATest should be executing garbage allocation)
Actual: activity is assigned to wrong coroutines (B.BTest is shown to be allocating GC)
Reproduced in: 2017.2.3p1, 2017.4.5f1, 2018.1.4f1, 2018.2.0b7
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
- Local keywords can be overridden by global keyword state
- Material Constructor doesn't copy ShaderKeyword from material properly
- IL2CPP error at Unity.IL2CPP.HashCodeCache`1.GetUniqueHash(T value) when building on Android
- [URP] [Debug View] [Mobile] Lighting Features - missing “Everything” checkbox (editor panel has it)
- [URP] [Debug View] [Mobile] Lighting Features - “None” can’t be marked
Mahgo
Jul 05, 2018 04:24
According to this there is a workaround. What is the workaround?