Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2018.2.10f1
Issue ID
1088161
Regression
No
[IL2CPP] Compiling with IL2CPP and 'script debugging enabled' the performance of code, even when not debugging is very poor
This cross-platform issue reproduces on all IL2CPP capable platforms, including 'PC, Mac & Linux Standalone'.
Performance of code is very poor if using IL2CPP with the 'Script Debugging' option enabled, even if you do not connect the debugger.
Steps to Reproduce
------------------------
1. Download the users reproduction project, project is already set to use .NET 4.x and IL2CPP
2. Open the 'TestScript.cs' script file, change line 27 from 'Debug.Log' to 'Debug.LogError' so the 'time to execute' is output to the screen.
3. In 'Build Settings' switch platform to 'PC, Mac & Windows Standalone'.
4. Turn off 'Script Debugging', leave 'Development Build' enabled.
5. Build for Windows Standalone
6. Run the game
Result #1 - without script debugging
The 'TestScript.cs' script takes ~0.26 seconds (260.7765ms) to complete.
7. Enable 'Script Debugging' in the build settings
8. Build for Windows Standalone
9. Run the game
Result #2 - with script debugging
The 'TestScript.cs' script takes ~19 seconds (19873.11ms) to complete.
Reproduced in
2018.2.15f1 (65e0713a5949)
2018.3.0b9 (a3326ae325b2)
2019.1.0a6 (370df4c90d4b)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Safe area ignores navigation bar on Android when targeting level 35 API or higher
- File watcher does not trigger after the AcquireFloatingLease and before the Entitlement check
- HDR Output gets disabled in the Editor when Reflection Probe is enabled during runtime
- The "Build and Run" Menu option tries to build for the selected Build Platform instead of the Active Build Platform
- Font kerning breaks at runtime when multiple UI Documents use different fonts
Add comment