Search Issue Tracker
Active
Votes
0
Found in
6.5.0-pre.2
Issue ID
UUM-137596
Regression
No
[AR Foundation] ArSession.Update() has very inconsistent (+-10ms) CPU time
Reproduction steps:
1. Open the attached “IN-137546“ project
2. Build and Run the iOS Player in Development Mode (with Deep Profiling Support disabled)
3. In the Player, open the “Camera” -> “CPU Images” scene
4. Inside the Editor, open the Profiler and select the iOS Player
5. In the Profiler Hierarchy view, search for “ARSession”
6. Observe the CPU time for “ARSession.Update()”
Actual result: CPU time constantly varies from 0.1 ms to over 11 ms
Expected result: Steady, consistent CPU time, varying up to +-1 ms
Reproducible with: 6.3.0 (6000.0.71f1), 6.3.3 (6000.3.11f1), 6.4.1 (6000.4.0f1), 6.5.0-pre.2 (6000.5.0a9, 6000.6.0a1)
Testing environment: macOS 26.3.1
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00634 - iPhone 15 Plus (MU0Y3QN/A), CPU: t8120, OS: 18.2.1
By reporter - iPhone 16 Pro Max
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment