Game: Longshot closed unexpectedly while you were playing #2078

Open
opened 2026-11-21 15:26:22 +00:00 by Charlie42 · 4 comments

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

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### 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 - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Charlie42 2026-11-21 15:26:22 +00:00
  • closed this issue
  • added the
    kind
    bug
    label
Contributor

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), then a C++ allocation refused (at the commit limit?).
  • longshot_log.2.txt: 1801 → 179 MB of commit left, then the renderer's allocation refused and VK_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), then FATAL: out of memory (RAM plus the page file).
  • longshot_log.txt: eight mem: 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:

  1. Give the page file a fixed, larger starting size. Go to Settings → System → About → Advanced system settings → Performance: Settings → Advanced → Virtual memory: Change, untick Automatically manage, choose the system drive, then Custom size: initial 16384 MB, maximum 24576 MB. Click Set, then restart Windows.
  2. Make sure the drive the page file is on has that much free space.
  3. Close what else holds a lot of memory while playing (browsers especially).

If it still crashes in the Market after that, please attach the new longshot_log.txt from 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.

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)`, then `a C++ allocation refused (at the commit limit?)`. - `longshot_log.2.txt`: 1801 → 179 MB of commit left, then the renderer's allocation refused and `VK_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)`, then `FATAL: out of memory (RAM plus the page file)`. - `longshot_log.txt`: eight `mem: 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:** 1. Give the page file a fixed, larger starting size. Go to *Settings → System → About → Advanced system settings → Performance: Settings → Advanced → Virtual memory: Change*, untick *Automatically manage*, choose the system drive, then *Custom size*: initial 16384 MB, maximum 24576 MB. Click *Set*, then restart Windows. 2. Make sure the drive the page file is on has that much free space. 3. Close what else holds a lot of memory while playing (browsers especially). If it still crashes in the Market after that, please attach the new `longshot_log.txt` from 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.*
No description provided.
Contributor

Same failure as #1280: vk: commit limit near: 16 MB of commit left (reserve 2560 MB), then vk: 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, with 96caf2f2 (#1885, nightly-695) and 0d476e58 (#2170, nightly-743) covering the stack and exception forms. fixed on nightly-745; this can be closed as a duplicate of #1280

Same failure as #1280: `vk: commit limit near: 16 MB of commit left (reserve 2560 MB)`, then `vk: 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, with `96caf2f2` (#1885, nightly-695) and `0d476e58` (#2170, nightly-743) covering the stack and exception forms. fixed on nightly-745; this can be closed as a duplicate of #1280
Contributor

Correction 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.

Correction 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.
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
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/Longshot#2078
No description provided.