-
Type:
Bug
-
Resolution: Declined
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS: Windows 11 (and WSL2)
node.js / npm versions: not installed (windows & WSL2)
Additional info:
-
Not Needed
-
None
-
Developer Tools
Problem Statement/Rationale
1.49.0 (both native windows and the .deb from within WSL2) has excessive GPU use. Not observed in 1.43.0 (WSL2)
Please be sure to attach relevant logs with any sensitive data redacted.
How to retrieve logs for: Compass; Shell
Steps to Reproduce
Fullscreen compass and watch the GPU graph spike in Task Manager.
Expected Results
Little to no discernible change in GPU usage when running compass (like in 1.43.0)
Actual Results
When full-screened on a 4K monitor usage spikes to about 40% (windows) or 80% (WSL2). A previous version (1.43.0) on WSL2 did not have this problem. My (external) GPU is an RTX3080 Ti. Internal GPU is Intel Arc. Both exhibits the same high-usage issues for screens it controls, though not to the same degree (about 20% GPU usage. High enough to set the laptop fan spinning). When compass is fullscreened on a monitor attached to the external GPU, the Intel ARC also has 10-25% GPU usage. When fullscreened on a 1080p monitor attached via display link, the internal ARC GPU usage shows about 9-10%, when on the laptop screen it uses about 5%.
Additional Notes
Any additional information that may be useful to include.
- duplicates
-
COMPASS-10281 Constant renders with new assistant icon
-
- Waiting (Blocked)
-