Search Issue Tracker
Fixed in 1.1.2
Votes
0
Found in [Package]
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1109865
Regression
Yes
EditMode tests performance downgrade in 2018.3 and later versions
Steps to reproduce:
1. Open original project "TestSpeed.zip"
2. Open Test Runner if not already open
3. Press "Run selected"
4. Observe TestSpeed
Expected results: TestSpeed would be similar or the same as 2018.2 versions (~0.080s).
Actual results: TestSpeed increases by a lot when Test Running in 2018.3(~0.250s)
Reproducible in: 2018.3.0a1, 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
Not Reproduced in: 2017.4.20f1, 2018.2.20f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Add comment