MagicBeanDev/Longshot

Watch

Fork 99

Game: Longshot closed unexpectedly while you were playing #862

New issue

Closed

opened 2026-11-15 18:06:39 +00:00 by MaikelJSQ · 2 comments

MaikelJSQ commented

2026-11-15 18:06:39 +00:00

Longshot version

nightly-189-aa95d35f (source 719431ac)

Channel

No response

What kind of problem

No response

What happened

Longshot closed unexpectedly while you were playing. Longshot ended without a crash report: it was closed from outside (Task Manager, a kill), or the system stopped it, often for running out of memory. (The report from the crash window is pasted below.)

Where in the game

Kokiri Forest

How often

No response

Graphics card and driver version

AMD Radeon RX 6600, AMD proprietary driver 26.10.1 (AMD proprietary shader compiler)

CPU, RAM and operating system

AMD Ryzen 5 5600G with Radeon Graphics (12 threads), 16 GB, Windows 11 (build 26200)

Changes from the defaults

No response

longshot_log.txt

[a64] unimplemented import ZN2nn2ro12ProtectRelroEPKvS2_S2_S2_S2 (lr 0x81237908)
[a64] unimplemented import _ZN2nn2vi36SetDisplay120HzRefreshRateCapabilityEPNS0_7DisplayEb (lr 0x8348bf64)
[hos host] longshot nightly-189-aa95d35f (source 719431ac)
[hos host] run_id: 9600400eddb1989f1de1e639507244f7
[hos host] crash window: watching this run (HOS_CRASH_WATCH=0: off)
[hos host] options: the settings file is C:\Users\maikj\AppData\Roaming\Longshot\longshot_options.ini
[hos host] oe: output resolution 1920x1080
[hos host] boot: widescreen: a 1.7778 screen is 16:9: the game's own picture
[hos host] boot: image 96 MB at 0x80000000, 9809 MB of memory for the game
[hos host] boot: 16274 MB of memory, 60416 MB of swap
[hos host] vk: reserved core selection: 6 cores, 12 logical, best class=0, fast cores=6, selected=0xc00
[hos host] vk: core 0: mask=0x3, class=0, popcount=2
[hos host] vk: core 1: mask=0xc, class=0, popcount=2
[hos host] vk: core 2: mask=0x30, class=0, popcount=2
[hos host] vk: core 3: mask=0xc0

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 nightly-189-aa95d35f (source 719431ac) ### Channel _No response_ ### What kind of problem _No response_ ### What happened Longshot closed unexpectedly while you were playing. Longshot ended without a crash report: it was closed from outside (Task Manager, a kill), or the system stopped it, often for running out of memory. (The report from the crash window is pasted below.) ### Where in the game Kokiri Forest ### How often _No response_ ### Graphics card and driver version AMD Radeon RX 6600, AMD proprietary driver 26.10.1 (AMD proprietary shader compiler) ### CPU, RAM and operating system AMD Ryzen 5 5600G with Radeon Graphics (12 threads), 16 GB, Windows 11 (build 26200) ### Changes from the defaults _No response_ ### longshot_log.txt [a64] unimplemented import _ZN2nn2ro12ProtectRelroEPKvS2_S2_S2_S2_ (lr 0x81237908) [a64] unimplemented import _ZN2nn2vi36SetDisplay120HzRefreshRateCapabilityEPNS0_7DisplayEb (lr 0x8348bf64) [hos host] longshot nightly-189-aa95d35f (source 719431ac) [hos host] run_id: 9600400eddb1989f1de1e639507244f7 [hos host] crash window: watching this run (HOS_CRASH_WATCH=0: off) [hos host] options: the settings file is C:\Users\maikj\AppData\Roaming\Longshot\longshot_options.ini [hos host] oe: output resolution 1920x1080 [hos host] boot: widescreen: a 1.7778 screen is 16:9: the game's own picture [hos host] boot: image 96 MB at 0x80000000, 9809 MB of memory for the game [hos host] boot: 16274 MB of memory, 60416 MB of swap [hos host] vk: reserved core selection: 6 cores, 12 logical, best class=0, fast cores=6, selected=0xc00 [hos host] vk: core 0: mask=0x3, class=0, popcount=2 [hos host] vk: core 1: mask=0xc, class=0, popcount=2 [hos host] vk: core 2: mask=0x30, class=0, popcount=2 [hos host] vk: core 3: mask=0xc0 ### 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.

longshot_log.txt

878 KiB

👀 1

MaikelJSQ added the

kind

bug

label

2026-11-15 18:06:39 +00:00

BeanIssues added the

gpu/amd

platform/windows

labels

2026-11-15 18:07:10 +00:00

BeanIssues commented

2026-11-15 18:07:11 +00:00

Collaborator

Possibly related, for context:

#854 Game: Longshot closed unexpectedly while you were playing — Same unclean-exit symptom on AMD/Windows while playing, but different GPU, driver, and location.
#861 Game: Longshot closed unexpectedly while you were playing — Same unclean-exit symptom and GPU family on Windows; different GPU model, game location, and version.

Possibly related, for context: - #854 Game: Longshot closed unexpectedly while you were playing — Same unclean-exit symptom on AMD/Windows while playing, but different GPU, driver, and location. - #861 Game: Longshot closed unexpectedly while you were playing — Same unclean-exit symptom and GPU family on Windows; different GPU model, game location, and version.

BeanIssues referenced this issue

2026-11-15 18:09:12 +00:00

Game: Longshot closed unexpectedly while you were playing #867

BeanIssues commented

2026-11-15 18:42:16 +00:00

Collaborator

This is the same problem as #859 (Game: Longshot closed unexpectedly while you were playing), so I'm closing this one to keep the discussion in one place.

Same person and same crash run (identical run_id): AMD RX 6600 on nightly-189 closing without a crash report in Kokiri Forest.

If it's different, say how and a maintainer will reopen it.

This is the same problem as #859 (Game: Longshot closed unexpectedly while you were playing), so I'm closing this one to keep the discussion in one place. Same person and same crash run (identical run_id): AMD RX 6600 on nightly-189 closing without a crash report in Kokiri Forest. If it's different, say how and a maintainer will reopen it.

BeanIssues

2026-11-15 18:42:17 +00:00