Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
819623
Regression
No
Drastic difference in performance of identical code between Unity-compiled script and externally compiled DLL assembly
Steps to reproduce:
1. Open "case_819623-PerfBug" project
2. Open "Test" scene
3. Play in editor
-- The editor will freeze as it is doing 8000 iterations in one frame. At the end of operation, you can notice a message with each DLL and Script execution time being printed.
Expected: Script time should approximately the same
Actual: Dll execution time takes way more time\
Note: Time difference is how much longer DLL execution took (it's not in seconds).
Reproduced with: 5.5.0a5, 5.4.0f3, 5.3.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment