Launcher: Window becomes unresponsive while building and scrolling the build log #201

Closed
opened 2026-11-18 13:18:52 +00:00 by BeanBot · 3 comments
Member

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

  1. Build Longshot v3.0.0-rc.7 in Longshot Launcher v1.0.0-rc.11.
  2. Change the log level to Debug and Trace, then back to Info.
  3. The whole launcher becomes unresponsive, then recovers after a minute or two.
  4. It became unresponsive again while scrolling the log, without changing the log level.

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

  • Whether the issue reproduces reliably and the exact actions/timing around the second occurrence
  • Windows build and NVIDIA driver version
  • Whether the launcher eventually recovers on the second occurrence
  • Whether the high CPU usage is sustained throughout the build or associated with particular build steps
Reported on [Discord](https://discord.com/channels/1569849200047427645/1572601344299241593/1572601344299241593) ## 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 1. Build Longshot v3.0.0-rc.7 in Longshot Launcher v1.0.0-rc.11. 2. Change the log level to Debug and Trace, then back to Info. 3. The whole launcher becomes unresponsive, then recovers after a minute or two. 4. It became unresponsive again while scrolling the log, without changing the log level. 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 - Whether the issue reproduces reliably and the exact actions/timing around the second occurrence - Windows build and NVIDIA driver version - Whether the launcher eventually recovers on the second occurrence - Whether the high CPU usage is sustained throughout the build or associated with particular build steps
Author
Member

Files from the Discord report:

Files from the Discord report: - [launcher.log](https://git.magicbean.dev/attachments/4c568050-8fd9-4ac2-8a81-ec2abf601442) - [image.png](https://git.magicbean.dev/attachments/49c06957-6eae-42df-9d15-1e3cadbc4c76)
Author
Member

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](https://discord.com/channels/1569849200047427645/1572601344299241593/1572602184967655465): 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.
Author
Member

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.

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1572601344299241593/1572602612090671166): Specified that the suggested conservative core-count defaults concern hybrid P-core/E-core CPUs and may reserve P-cores for system responsiveness.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/LongshotLauncher#201
No description provided.