Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.10f1
2023.1.15f1
2023.2.0b11
2023.3.0a7
Issue ID
UUM-52508
Regression
Yes
Player performance spikes when it is running on high-resolution monitors
Reproduction steps:
1. Open the attached project “URPTest”
2. Open the “Assets/TerrainDemoScene_URP/Scenes/TerrainDemoScene” Scene
3. Open the Build Settings window (File > Build Settings)
4. In the Build Settings window check the “Development Build” checkmark
5. Build the project
6. Launch the built Player
7. In Editor open the Profiler window (Window > Analysis > Profiler)
8. Connect the Profiler to the launched Player
9. Focus the Player to let it run and observe the Profiler window for a few minutes
Expected result: The Player performance is steady with no big spikes
Actual result: The Player periodically experiences performance spikes that take 25 ms or more of CPU time
Reproducible with: 2022.3.10f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a7
Not reproducible with: 2021.3.30f1
Reproducible on: Windows 10
Couldn’t test on: macOS 13.5.2 (Intel) - The Player performance was too poor to see noticeable spikes
Note: For a higher reproduction rate use monitors that are 4k or higher, it is still reproducible on 1440p, but the reproduction rate is much lower
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Could not reproduce.