Game: Longshot closed unexpectedly while you were playing #2078
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#2078
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?
Longshot version
v3.0.0 (source 87cb36aa)
Channel
Release
What kind of problem
Crash, freeze or black screen
What happened
Longshot closed unexpectedly while you were playing. An unexpected error. (The report from the crash window is pasted below.)
Where in the game
Market_Child (child)
How often
Every time
Graphics card and driver version
NVIDIA GeForce RTX 3060 Ti, NVIDIA 621.01
CPU, RAM and operating system
13th Gen Intel(R) Core(TM) i5-13400F (16 threads), 16 GB; Windows 11 (build 26300)
Changes from the defaults
No response
longshot_log.txt
1
Screenshots or video
No response
Before you send it
All four of the small logs show the same cause: Windows ran out of commit (RAM plus the page file) in the child Market.
longshot_log.1.txt:vk: commit limit near: 16 MB of commit left (reserve 2560 MB), thena C++ allocation refused (at the commit limit?).longshot_log.2.txt: 1801 → 179 MB of commit left, then the renderer's allocation refused andVK_ERROR_DEVICE_LOST. The driver, too, couldn't get memory.longshot_log.3.txt:native NVN: recording copy: 2097152 bytes of host memory still refused after 5 s at the commit limit (5 MB of commit left), thenFATAL: out of memory (RAM plus the page file).longshot_log.txt: eightmem: commit of ... at the commit limit made after ...waits.At the start, the log says
commit: 2386 MB left under Windows' limit as it is now, and the page files can grow by 5470 MB more. So with 16 GB of RAM, Longshot relies on the page file growing, and in the Market it needs more than Windows grows it in time (or more than the drive has room for). That's why it happens every time there and not elsewhere.What should fix it for the reporter, @Charlie42:
If it still crashes in the Market after that, please attach the new
longshot_log.txtfrom the crash. It shows the commit left at the start.The same limit gives a different crash in #1772 (a stack overflow,
0xc00000fd), which #1885 handles. This one is the renderer's and the driver's own allocations, which need the memory itself.Posted by an AI agent (Claude Code) for d4nkn3ss.
Same failure as #1280:
vk: commit limit near: 16 MB of commit left (reserve 2560 MB), thenvk: a C++ allocation refused (at the commit limit?): tried again for up to 5 s— Windows out of commit in the child Market.f88e6e3a(#1291) covers this from v3.0.0-rc.7, with96caf2f2(#1885, nightly-695) and0d476e58(#2170, nightly-743) covering the stack and exception forms. fixed on nightly-745; this can be closed as a duplicate of #1280Correction to my earlier comment: #1280 is closed, so please close this against the open home #1443, not #1280. The covering commit/nightly quoted above is unchanged.