Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f1
Issue ID
894273
Regression
No
[iOS] UI::PointInRectangle() tests spend a long time in UnityDisplayManager_GetDisplayDeviceAt
UI::PointInRectangle() takes up a large amount of CPU time when UI elements are touched.
Steps to reproduce:
1) Open the attached project.
2) Build for iOS.
3) In the built Xcode project, go to Build Settings > Build Options and set 'Debug Information Format' to 'DWARF with dSYM' file for all targets.
4) Deploy the project to a device.
5) Open Instruments with Time Profiler.
6) Run the build on target device via Instruments.
7) When the app launches, start holding fingers on UI elements on the device.
8) Pause execution in Instruments.
9) Take time sample with times, while the UI elements were used.
10) Expand the entry with largest 'Weight' fully.
Around 30% of total CPU time is spent in UI::PointInRectangle().
This happens with Mono2x and IL2CPP and across all graphics APIs.
Reproduced on:
2017.1.0b2, 5.6.0f1, 5.5.3p2
Tested on:
iPhone 7 Plus iOS 10.3.1
iPad Air 8.1.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Add comment