Install: Intel Arc A730 shader and pipeline preparation takes hours #1706
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
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/Longshot#1706
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
The reporter is building Longshot v3.0.0 in Longshot Launcher and shader preparation is taking an extreme amount of time. At the screenshot, the launcher showed 88% overall, shader preparation at 69%, elapsed 1:14:15, with about 32 minutes estimated remaining. A separate loading-screen screenshot for Longshot v3.0.0-rc.7 showed pipeline loading at 12,750 / 36,682 (34%) with about 1,187 minutes remaining. The reporter observed GPU utilization at 5% (70 °C). They reinstalled, selected side-by-side shader building, and updated the driver; shader preparation still took a long time. A screenshot later showed the launcher apparently unresponsive at 62% of building v3.0.0-rc.8 (about 6 minutes remaining); the visible log reports preparation using 10 workers on a 20-CPU system and Intel shader compilation side by side. The reporter eventually built it and began in-game shader preparation.
The reporter then said the game loads the intro, drops FPS and freezes on a black screen. The attached crash report is for v3.0.0 release, Windows 11 build 26300, Vulkan, Intel Arc A730M driver 101.9175, i7-12700H and 16 GB RAM. It reports an unclean end (no crash/device-lost record), and the report says it may have been stopped externally or by the system, often due to memory exhaustion. It does not establish OOM as the cause. The game map at report time is KokiriForest_Child. Settings include handheld profile, 1280x800 output, and GPU device 1; the reporter says the intro played perfectly before the FPS drop and freeze.
What they used / versions
Longshot Launcher nightly 140 · 87b70727 was shown during build; the build screen showed v3.0.0-rc.8. The crash report is for Longshot v3.0.0 Release (source 87cb36aa). Driver version 32.0.101.9175 WHQL, released 2026-11-04.
System
Intel Arc A730M Graphics, driver 101.9175; Intel Iris Xe also appears in the device list. Windows 11 build 26300, 12th Gen Intel Core i7-12700H (20 threads), 16 GB RAM.
Not known yet
logs/longshot_log.txtcovering the freeze and performance/profile measurements during the drop.Attachments
The crash report from Discord message 1572868089404465353 is attached as
message.txt.Files from the Discord report:
From #1717 (closed as a duplicate of this one):
The same reporter's v3.0.0 release-candidate run on Windows 11 (build 26300), Intel Arc A730M, driver 101.9175, i7-12700H and 16 GB RAM ended without a crash report while preparing shaders. The log shows pipeline preparation still active after roughly 78 minutes, at about 44% (15,000/34,809), with estimated remaining time fluctuating by hours. This adds evidence the prolonged A730 shader/pipeline preparation can end in an unexpected process termination; the unclean record does not establish whether the cause was OOM or an external/system termination.
Updated with more from Discord: Added crash report/system details and the post-build intro-to-black-screen freeze; attached the crash report. It records an unclean termination but does not prove OOM.
Files:
From Discord:
The reporter says shader compilation has been running for 40 minutes and was still ongoing; they went for a walk while waiting. No GPU, driver, Longshot version/channel, operating system, or log was provided.