Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2022.1
2022.1.0a6
Issue ID
1362108
Regression
No
Built Project uses ~100% of GPU when launched through Command Prompt with "-hideWindow"
How to reproduce:
1. Create a new empty project
2. Go into File -> Build Settings...
3. Press the "Build" button
4. Open Command Prompt in the build location
5. Start the build with " -hideWindow", through the console
6. Open Task Manager
Expected result: Acceptable amount of GPU usage ~0-10%
Actual result: Immense GPU usage ~50-100%
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b15, 2022.1.0a11
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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note:
GPU usage is directly proportional to frame rate. With "-hideWindow", VSync doesn't work (because there's nothing to sync to - the image doesn't reach the screen) so you have to limit frame rate some other way.