Game: Longshot uses all system RAM during gameplay #1014

Open
opened 2026-11-16 02:28:26 +00:00 by BeanIssues · 8 comments
Collaborator

Reported by José preto in a DM to the bot on Discord

Longshot version and channel

v3.0.0-rc.4, release candidate.

What happened

The game consumes 100% of the system RAM despite the PC having 32 GB. The reporter says the problem persists on v3.0.0-rc.4.

What is still unknown

  • When this happens (immediately or after playing), where in the game, and how often
  • Whether RAM usage stays high after closing Longshot
  • GPU and driver version, CPU, and operating system
  • longshot_log.txt from the game's logs folder (or an in-game Bug report folder)

Open PR #637 concerns VRAM management on GPUs with less than 8 GB of VRAM; it is not yet merged and does not establish a fix for this system-RAM report.

Reported by José preto in a DM to the bot on Discord ### Longshot version and channel v3.0.0-rc.4, release candidate. ### What happened The game consumes 100% of the system RAM despite the PC having 32 GB. The reporter says the problem persists on v3.0.0-rc.4. ### What is still unknown - When this happens (immediately or after playing), where in the game, and how often - Whether RAM usage stays high after closing Longshot - GPU and driver version, CPU, and operating system - `longshot_log.txt` from the game's logs folder (or an in-game Bug report folder) ### Related work Open PR [#637](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/637) concerns VRAM management on GPUs with less than 8 GB of VRAM; it is not yet merged and does not establish a fix for this system-RAM report.
Contributor

For comparison, what this looks like on a PC that doesn't run out (Windows 11, RTX 3080 10 GB, 64 GB RAM, main @ a8a30c22, a 43-minute two-lap tour through eight areas):

  • The game's commit charge ("Commit size" in Task Manager's Details tab, what counts against RAM plus the page file) settles at about 20 GB after the first area changes and doesn't grow over the second lap. About 7.6 GB of that is the game's own memory. About 7.5-8 GB is the VRAM blocks: on NVIDIA, Windows charges every block of video memory to the process's commit as well, though it uses no RAM. The rest of the host is about 4.3 GB.
  • The working set (RAM actually in use, Task Manager's "Memory" column) peaked at about 11-12 GB.

So on a 32 GB PC, "all the RAM" is worth pinning down. Which Task Manager column was full (Memory, or Commit size, or the Performance tab's "In use" or "Committed")? Was it right after loading a save or after a long session? The longshot_log.txt lines that answer it are vk: memory: working set ... private ..., vk: imports: ... and vk: memory heaps: ..., printed every few hundred frames. The first and last of each are enough. #992 makes scripts/memtour.py split the commit this way on Windows, for anyone who can run a tour. Worklist row 5.6 has the numbers above.

Posted by an AI agent (Claude Code) for d4nkn3ss.

For comparison, what this looks like on a PC that doesn't run out (Windows 11, RTX 3080 10 GB, 64 GB RAM, main @ a8a30c22, a 43-minute two-lap tour through eight areas): - The game's **commit charge** ("Commit size" in Task Manager's Details tab, what counts against RAM plus the page file) settles at about **20 GB** after the first area changes and doesn't grow over the second lap. About 7.6 GB of that is the game's own memory. About 7.5-8 GB is the **VRAM blocks**: on NVIDIA, Windows charges every block of video memory to the process's commit as well, though it uses no RAM. The rest of the host is about 4.3 GB. - The **working set** (RAM actually in use, Task Manager's "Memory" column) peaked at about 11-12 GB. So on a 32 GB PC, "all the RAM" is worth pinning down. Which Task Manager column was full (Memory, or Commit size, or the Performance tab's "In use" or "Committed")? Was it right after loading a save or after a long session? The `longshot_log.txt` lines that answer it are `vk: memory: working set ... private ...`, `vk: imports: ...` and `vk: memory heaps: ...`, printed every few hundred frames. The first and last of each are enough. https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/992 makes `scripts/memtour.py` split the commit this way on Windows, for anyone who can run a tour. Worklist row 5.6 has the numbers above. *Posted by an AI agent (Claude Code) for d4nkn3ss.*
Author
Collaborator

From a DM to the bot on Discord from josep2409:

The reporter adds that they have an RTX 5060, an Intel Core i5-14600KF, and 32 GB RAM. They say Longshot starts at about 25 GB RAM usage, rises until it reaches 32 GB, and then stutters/freezes. They did not provide OS, GPU driver version, game location/session duration, whether usage remains high after closing, or longshot_log.txt.

From a DM to the bot on Discord from `josep2409`: The reporter adds that they have an RTX 5060, an Intel Core i5-14600KF, and 32 GB RAM. They say Longshot starts at about 25 GB RAM usage, rises until it reaches 32 GB, and then stutters/freezes. They did not provide OS, GPU driver version, game location/session duration, whether usage remains high after closing, or `longshot_log.txt`.
Author
Collaborator

From a DM to the bot on Discord from josep2409:

The reporter adds: closing Longshot returns RAM usage to normal; reopening it starts around 25 GB again. They see 50–60 FPS when opening the game, then 15–20 FPS in the same area after 10–20 minutes. Reported hardware: RTX 5060, Intel Core i5-14600KF, 32 GB RAM; Longshot v3.0.0-rc.4.

Still needed: OS, GPU driver version, longshot_log.txt (ideally with vk: memory: working set, vk: imports, and vk: memory heaps readings before and after slowdown), and which Task Manager RAM/commit metric reaches 32 GB.

From a DM to the bot on Discord from `josep2409`: The reporter adds: closing Longshot returns RAM usage to normal; reopening it starts around 25 GB again. They see 50–60 FPS when opening the game, then 15–20 FPS in the same area after 10–20 minutes. Reported hardware: RTX 5060, Intel Core i5-14600KF, 32 GB RAM; Longshot v3.0.0-rc.4. Still needed: OS, GPU driver version, `longshot_log.txt` (ideally with `vk: memory: working set`, `vk: imports`, and `vk: memory heaps` readings before and after slowdown), and which Task Manager RAM/commit metric reaches 32 GB.
Author
Collaborator

From a DM to the bot on Discord from josep2409:

Reporter adds: Windows 11; RTX 5060 with the latest driver (exact driver version not specified).

From a DM to the bot on Discord from `josep2409`: Reporter adds: Windows 11; RTX 5060 with the latest driver (exact driver version not specified).
Author
Collaborator

From a DM to the bot on Discord from josep2409:

Reporter says Task Manager shows Longshot using 98% of RAM. The exact Task Manager metric/column remains unclear; no longshot_log.txt has been supplied.

From a DM to the bot on Discord from `josep2409`: Reporter says Task Manager shows Longshot using 98% of RAM. The exact Task Manager metric/column remains unclear; no `longshot_log.txt` has been supplied.
Author
Collaborator

From a DM to the bot on Discord from josep2409:

Reporter asks whether they can resolve this themselves or must wait for an update. No confirmed workaround or fix is known. They can help investigation by attaching longshot_log.txt with readings before/after FPS drops, clarifying which Task Manager metric reaches 98%, and giving the exact NVIDIA driver version.

From a DM to the bot on Discord from `josep2409`: Reporter asks whether they can resolve this themselves or must wait for an update. No confirmed workaround or fix is known. They can help investigation by attaching `longshot_log.txt` with readings before/after FPS drops, clarifying which Task Manager metric reaches 98%, and giving the exact NVIDIA driver version.
Author
Collaborator

From a DM to the bot on Discord from josep2409:

Reporter tested v3.0.0-rc.5; the same RAM/performance problem recurred. They will try to record the next occurrence. Please attach a recording and, ideally, an in-game Bug report/longshot_log.txt captured during the slowdown. Still useful: the specific Task Manager metric, graphics settings, and memory log lines before/after the FPS drop.

From a DM to the bot on Discord from `josep2409`: Reporter tested v3.0.0-rc.5; the same RAM/performance problem recurred. They will try to record the next occurrence. Please attach a recording and, ideally, an in-game Bug report/longshot_log.txt captured during the slowdown. Still useful: the specific Task Manager metric, graphics settings, and memory log lines before/after the FPS drop.
Author
Collaborator

From Discord:

Discord report: Task Manager Performance > Memory showed 28.0/31.8 GB in use (88%), 43.6/45.3 GB committed, and 3.8 GB available during play. Screenshot attached. No game version, OS/GPU details, or game log supplied in this report.

From [Discord](https://discord.com/channels/1569849200047427645/1569849200617726065/1571916668085608578): Discord report: Task Manager Performance > Memory showed 28.0/31.8 GB in use (88%), 43.6/45.3 GB committed, and 3.8 GB available during play. Screenshot attached. No game version, OS/GPU details, or game log supplied in this report.
Sign in to join this conversation.
No milestone
No project
No assignees
2 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#1014
No description provided.