Game: Arc 130V crashes after extreme slowdown during cutscene #938
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#938
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 by Marco Loves 360 on Discord
Longshot version
nightly-189-aa95d35f (source 719431ac)
Channel
Nightly
What happened
Longshot slowed to a crawl during a cutscene, continued moving very slowly for a while, then crashed. The crash report says: “The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game.” The crash record reason is
device lost.Where in the game
During a cutscene; exact scene not provided.
How often
The player reports being stuck on the cutscene a few times before it eventually crashed. Exact frequency not provided.
Graphics card and driver version
Intel(R) Arc(TM) 130V GPU (8GB), Intel Corporation 101.9175
CPU, RAM and operating system
Intel(R) Core(TM) Ultra 5 226V (8 threads), 16 GB, Windows 11 (build 26200)
Settings
Player reports using 6 GB dedicated VRAM, leaving 10 GB RAM, and 50% resolution scaling. The generated crash report also lists
output_res=1920x1200,resolution=4,upscaling=0,threaded_rendering=0, andmemory_budget=1.longshot_log.txt
The game log records that the GPU finished nothing for 30 seconds, followed by
GPU hanganddevice lost. The crash report shows uptime of 1416 seconds. See attached game log.Related issue
Longshot #878 reports a device-lost crash on an Intel Arc 140V with the same driver version, but on a different model and at a different point in gameplay.
Files from the Discord report:
i tried again and crashed earlier, might be running out of ram?