Search Issue Tracker
Fixed in 2018.3.8f1
Fixed in 2018.3, 2019.1, 2019.2
Votes
0
Found in
2017.3.0a1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1111339
Regression
No
[IL2CPP] System.Threading.WaitHandle.WaitOne is slower compared to Editor or mono backend
Steps to reproduce:
1. Download 1111339_repro.zip and open "Startup" scene
2. Enter play mode
3. Notice that Main Update times is 20-22 ms
4. Build a Standalone project with IL2CPP backend
5. Notice that Main Update time is 33-51ms
Expected results: Performance of System.Threading.WaitHandle.WaitOne on IL2CPP should be similar to Editor or mono
Actual results: On IL2CPP backend System.Threading.WaitHandle.WaitOne is more than 2 times slower.
Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2017.4.18f1
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
- [Xcode12][Burst] iOS builds with Universal/ARMv7 architecture fail in Xcode 12 with New Build System when using burst
- Changing scale of Tree prefab instance (in scene) and then undo/redo changes the source prefab scale and all painted instances
- Material properties are not correctly setup when assigning a ShaderGraph to a newly created material
- [iOS] Device.generation returns "DeviceUnknown" with some devices
- Misleading upgrade prompt when opening Project from Hub with an incremented project version
Resolution Note (fix version 2018.3.8f1):
Fixed in: 2019.2.0a6, 2019.1.0b5, 2018.3.8f1