Game: Water Temple loading freezes on a low-RAM Linux laptop #91

New issue

Open

opened 2026-11-13 02:27:28 +00:00 by mooki · 0 comments

mooki commented

2026-11-13 02:27:28 +00:00

Longshot version

Carried from Hookshot v2.1.0. Longshot main 6b2dafefe has no demonstrated fix for this report; the related warning proposal is still open.

What kind of problem

Crash, freeze or black screen

What happened

spudjunko reported a black-screen freeze while entering the Water Temple that left the game unclosable and led them to restart the PC. A later comment reports another incident. The two attached files are byte-identical and end with the ordinary “window closed, exiting” line: they are not two captured failures and establish neither an OOM kill nor a GPU crash.

I took this on and posted the findings and a bounded memory-pressure comparison. The log reports 7,639 MiB physical RAM and 32,767 MiB swap; the form's 32 GB is not confirmed physical RAM. On my different Linux/NVIDIA PC, an isolated game limited to 7,639 MiB RAM and 8 GiB swap filled its swap and stalled after the accepted temple transition; a 24-GiB control loaded it. This supports a memory-pressure lead, not a diagnosis of the laptop or its larger swap setup.

Longshot pull request 54 fixes the related missing startup warning: main treats RAM plus swap as sufficient above 10 GiB. It does not reduce allocations, fix the stall or close this report. The original proposal was GitHub pull request 2901.

Missing evidence: the failed session's log, actual free RAM/swap, and kernel OOM or NVIDIA fault lines around the failure. No system-wide swap or memory-setting change is justified by these attachments alone. No current Longshot gameplay reproduction on this laptop has been supplied.

Where in the game

Loading screen before entering the Water Temple.

How often

Original form: once. A later comment reports another incident without a distinct failure log.

Graphics card and driver version

Reporter: RTX 4050 Laptop, NVIDIA 595.99. My bounded comparison used RTX 4090/NVIDIA 615.78.08, not the same hardware.

CPU, RAM and operating system

Reporter: Core i5-13420H, Linux. Form says 32 GB; startup log says 7,639 MiB RAM plus 32,767 MiB swap. Distribution and failure-time memory use remain unknown.

Changes from the defaults

None supplied in the form. The comparison's isolated RAM/swap limits differ from the reporter's machine and are not recommended player settings.

Other software hooked into the game

Reporter says none. Normal-exit attachments remain linked from the original report; failed-session evidence is missing.

Reported on GitHub as NotRexed/Hookshot#2838; taken on there by mooki.

### Longshot version Carried from Hookshot v2.1.0. Longshot main `6b2dafefe` has no demonstrated fix for this report; the related warning proposal is still open. ### What kind of problem Crash, freeze or black screen ### What happened [spudjunko reported](https://github.com/NotRexed/Hookshot/issues/2838) a black-screen freeze while entering the Water Temple that left the game unclosable and led them to restart the PC. A later comment reports another incident. The two attached files are byte-identical and end with the ordinary “window closed, exiting” line: they are not two captured failures and establish neither an OOM kill nor a GPU crash. I took this on and [posted the findings and a bounded memory-pressure comparison](https://github.com/NotRexed/Hookshot/issues/2838#issuecomment-6833217794). The log reports 7,639 MiB physical RAM and 32,767 MiB swap; the form's 32 GB is not confirmed physical RAM. On my different Linux/NVIDIA PC, an isolated game limited to 7,639 MiB RAM and 8 GiB swap filled its swap and stalled after the accepted temple transition; a 24-GiB control loaded it. This supports a memory-pressure lead, not a diagnosis of the laptop or its larger swap setup. [Longshot pull request 54](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/54) fixes the related missing startup warning: main treats RAM plus swap as sufficient above 10 GiB. **It does not reduce allocations, fix the stall or close this report.** The original proposal was [GitHub pull request 2901](https://github.com/NotRexed/Hookshot/pull/2901). Missing evidence: the failed session's log, actual free RAM/swap, and kernel OOM or NVIDIA fault lines around the failure. No system-wide swap or memory-setting change is justified by these attachments alone. No current Longshot gameplay reproduction on this laptop has been supplied. ### Where in the game Loading screen before entering the Water Temple. ### How often Original form: once. A later comment reports another incident without a distinct failure log. ### Graphics card and driver version Reporter: RTX 4050 Laptop, NVIDIA 595.99. My bounded comparison used RTX 4090/NVIDIA 615.78.08, not the same hardware. ### CPU, RAM and operating system Reporter: Core i5-13420H, Linux. Form says 32 GB; startup log says 7,639 MiB RAM plus 32,767 MiB swap. Distribution and failure-time memory use remain unknown. ### Changes from the defaults None supplied in the form. The comparison's isolated RAM/swap limits differ from the reporter's machine and are not recommended player settings. ### Other software hooked into the game Reporter says none. Normal-exit attachments remain linked from the original report; failed-session evidence is missing. Reported on GitHub as NotRexed/Hookshot#2838; taken on there by mooki.