Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X, 2018.1.X
Votes
0
Found in
2017.3.0p1
Issue ID
989476
Regression
No
[iOS] MonoManager::GetScriptingClass takes a lot of Unity loading time
Reproduction Steps:
1. Build project for iOS (building steps in edit)
2. In Xcode build (profile) and launch Instruments
3. Instruments select "Time Profiler"
4. Record/Profile
5. Select first 10 seconds
6. Notice that MonoManager::GetScriptingClass takes a lot of time
Expected behaviour: Optimal Unity application loading
Actual result: Loading Unity application string allocations/deallocations/comparisons takes a lot of time.
Reproduced on versions: Unity 2017.3.0f3, 2017.3.0p3
Project crashed on opening with Unity 2018
Reproduced on devices: iPhone 7 Plus iOS 10.3.2, iPhone 5 iOS 10.1.1, iPhone 4s iOS 8.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Local keywords can be overridden by global keyword state
- Material Constructor doesn't copy ShaderKeyword from material properly
- IL2CPP error at Unity.IL2CPP.HashCodeCache`1.GetUniqueHash(T value) when building on Android
- [URP] [Debug View] [Mobile] Lighting Features - missing “Everything” checkbox (editor panel has it)
- [URP] [Debug View] [Mobile] Lighting Features - “None” can’t be marked
Add comment