Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.5f1
Issue ID
1076284
Regression
No
[IL2CPP] Some methods cause application to run slow on Hololens when Scripting Backend is IL2CPP
How to reproduce:
1. Open the attached "1076284_repro.zip" project
2. Set the Target Platform to "UWP"
3. In the Build Settings, enable Development Build, Autoconnect Profiler, and Script Debugging options
4. In the Publishing Settings, enable InternetClient, InternetClientServer, and PrivateNetworkClientServer capabilities
5. Set the Scripting Backend to ".NET"
6. Build the project and run on Hololens
7. Observe the Profiler data in the Unity Editor
8. Set the Scripting Backend to "IL2CPP"
9. Again, build the project and run on Hololens
10. Observe the Profiler data in the Unity Editor
Expected result: Setting Scripting Backend to IL2CPP does not result in the worse application performance.
Actual result: Application runs slower when Scripting Backend is set to IL2CPP.
Reproducible with - 2018.2.11f1, 2018.3.0b4, 2019.1.0a3
Note: The methods that were used when reproducing the issue are a part of BoundingBox (from MixedRealityDesignLabs) functionality.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment