Launcher: Window becomes unresponsive while building and scrolling the build log #201
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher#201
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported on Discord
What happened
While building Longshot, changing the log level from Debug/Trace back to Info made the whole launcher stop responding. It recovered after a minute or two. The launcher later showed “Not responding” again without another log-level change, after the reporter only scrolled the log. The reporter additionally observed CPU usage at 92%, even after lowering the build core count to about 12, and suggests more conservative defaults for high-core CPUs with performance cores. They clarify that by this they specifically mean hybrid CPUs with P-cores and E-cores: account for E-cores when choosing build parallelism, potentially use only P-cores and leave one or two P-cores free for the system.
Steps / frequency
The screenshot shows the build at 53%, the log-level menu, and “About 10 min left.” The reporter says this happened again; whether it is consistently reproducible is unknown.
System
Windows 11, Intel Core i9-12900K, NVIDIA GeForce RTX 3080 Ti. Build core count was lowered to about 12; other settings were default. CPU usage reached 92%. The CPU has P-cores and E-cores.
Launcher log
The attached launcher log shows startup, successful release/tool downloads, and the supported game-file check. It contains no explicit error or exception explaining the unresponsiveness.
Still unknown
Files from the Discord report:
Updated with more from Discord: Added CPU usage of 92% despite reducing build core count to about 12, and the suggestion for more conservative defaults on high-core CPUs with performance cores.
Updated with more from Discord: Specified that the suggested conservative core-count defaults concern hybrid P-core/E-core CPUs and may reserve P-cores for system responsiveness.