Game: Longshot uses all system RAM during gameplay #1014
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#1014
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 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
longshot_log.txtfrom the game's logs folder (or an in-game Bug report folder)Related work
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.
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):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.txtlines that answer it arevk: memory: working set ... private ...,vk: imports: ...andvk: memory heaps: ..., printed every few hundred frames. The first and last of each are enough. #992 makesscripts/memtour.pysplit 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.
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: 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 withvk: memory: working set,vk: imports, andvk: memory heapsreadings before and after slowdown), and which Task Manager RAM/commit metric reaches 32 GB.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 says Task Manager shows Longshot using 98% of RAM. The exact Task Manager metric/column remains unclear; no
longshot_log.txthas been supplied.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.txtwith 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 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 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.