Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2017.3.0a1
2018.2.14f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1099027
Regression
No
Using .NET API 4.x increases performance spike in Scripts twice when selecting an object with a script for the first time
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Open the Profiler and enable "Deep Profile" and "Profile Editor"
3. Record and Enter Play mode
4. Click on "GameObject" in the Hierarchy window
5. Turn off Record and Exit Play mode
6. Notice a spike of ~800ms in Scripts
7. Change the Scripting Runtime Version to .NET API 4.x
8. Repeat steps 2-6
9. Notice a spike of ~1600ms in Scripts
Expected Result: .NET API 4.x has the same performance as .NET API 3.5
Actual Result: Using .NET API 4.x decreases performance in Scripts twice
Reproduced with: 2019.2.0a4, 2019.1.0b2, 2018.3.5f1, 2017.4.20f1
Note:
The script attached to the "GameObject' just has a public GameObject
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Add comment