Search Issue Tracker
Won't Fix
Votes
0
Found in
5.1.1p1
Issue ID
711838
Regression
No
[IL2CPP,iOS] CPU time taken Debug.Log depends on call stack depth
To Reproduce:
1. Attach the script 'DebugLogTest.cs' to any gameobject (uncomment BeginSample/EndSample).
2. Run and connect the profiler.
3. Observe that Debug.Log calls become increasingly more expensive when they are called recursively. Something similar is also noticeable on mono backed, but the increase is much smaller.
Tested on iPad Mini 2 (iOS 8.4) :
IL2CPP:
cpu time/recursion level
8.74ms@100
6.57ms@75
3.51ms@50
1.77ms@25
0.28ms@2
mono:
0.33ms@100
0.27ms@75
0.17ms@50
0.11ms@25
0.08ms@2
Not reproducible in editor - all Debug.Log calls take more or less the same independent from depth
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
- Editor hangs when opening Asset picker window for AssetReference and a lot of addresable assets are present in the project
Add comment