Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.23f1
2021.2.5f1
2022.2.0b7
Issue ID
UUM-2517
Regression
No
[iOS] Camera.Render takes 14 times more CPU time when device is rotated
How to reproduce:
1. Open the attached project ("My project (2).zip")
2. Build And Run on an iOS device
3. Open Profiler (Window -> Analysis -> Profiler)
4. Select device as Profiler target
5. Rotate device until in Timeline, Camera.render is shown as taking around 16ms of time
Expected result: Render thread is waiting
Actual result: Camera.Render is taking up time
Reproducible with: 2019.4.33f, 2020.3.23f1, 2021.2.5f1, 2022.1.0a16
Reproducible on:
iPhone 13 mini (iOS 15)
iPhone 8 Plus (iOS 14.4.2)
Not reproducible on:
iPad Air 2 (iOS 11.0.3)
Huawei - (ELS-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
Note:
- The Profiler results were different from the ones in the user's screenshots when testing with Android devices
- It may take a few tries to reproduce the issue (repeat from step 2)
-
JesterGameCraft
Feb 08, 2022 19:48
Just wanted to ask if there is any progress on this issue. This behaviour makes it hard to profile reliably/consistently on iOS.
-
Peter77
Dec 03, 2021 18:50
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Crash on pthread_kill when using incremental GC
- "Broken text PPtr in file(Assets/GemHunterMatch/Characters/Mermaid/Animations/Controller_PSD_character_mermaid.controller)" is thrown when importing "Gem Hunter Match - 2D Sample Project" into the project
- .wav and .ogg audio files can't be imported to the project when the WebGL Build Profile is selected
- [VFX Graph] Capacity Issue when using GPUEvent and Strips.
- Requested destroyCancellationToken reports as not requested when not called before destroyed
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.