Game: Longshot closed unexpectedly while you were playing #1923
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1923
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?
Longshot version
v3.0.0 (source 87cb36aa)
Channel
Nightly
What kind of problem
Something else
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
KakarikoVillage_Child (child)
How often
Every time
Graphics card and driver version
NVIDIA GeForce RTX 3050, NVIDIA 560.94
CPU, RAM and operating system
Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (12 threads), 16 GB; Windows 10 (build 19045)
Changes from the defaults
No response
longshot_log.txt
Longshot crash report, made by the window Longshot shows after a crash (20261120T214549Z UTC). Longshot sent nothing: paste this into the issue form, and attach the game folder's logs/longshot_log.txt if you can.
What happened
Longshot closed unexpectedly while you were playing.
What went wrong: 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.
Crash and unclean-end records in the last day: 3.
Summary (what Report automatically sends, too)
Version: v3.0.0
Release build: Yes
Operating system: Windows 10 (build 19045)
Renderer: Vulkan
Graphics card: NVIDIA GeForce RTX 3050, NVIDIA 560.94
CPU and RAM: Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (12 threads), 16 GB
Map: KakarikoVillage_Child (child)
Settings: 112, 0 changed from the defaults
Crash: unknown
Log: its end, below
Longshot version
v3.0.0 (source 87cb36aa)
Channel (from the version): Release
Graphics card and driver version
NVIDIA GeForce RTX 3050, NVIDIA 560.94
Devices the log lists: NVIDIA GeForce RTX 3050
CPU, RAM and operating system
Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (12 threads), 16 GB, Windows 10 (build 19045)
Built for: this PC's CPU (broadwell_broadwell_861cd1e4e7)
Upscalers (the log's first line of each)
NVIDIA DLSS: NGX started (DLSS's runtime: the newest nvngx_dlss.dll in D:\Zelda OOTR\rc\ngx, %USERPROFILE%\AppData\Local\Longshot\ngx)
AMD FSR 4: not named in the log
Changes from the defaults
longshot_options.ini (a value only when it is a number or on/off; the controls' bindings left out):
quality_preset=0
ultrawide=1
output_res=1920x1080
handheld_profile=0
dlss=2
dlss_model=0
dlss_pre_bloom=0
resolution=0
sharpness=30
frame_generation=0
frame_generation_by=1
frame_rate_cap=0
nvidia_reflex=1
fullscreen=1
vsync=2
upscaling=1
crt_filter=0
crt_lines=0
ultrawide_menus=1
hud_layout=0
hdr=1
hdr_paper_white=200
hdr_peak_brightness=1000
hdr_contrast=100
hdr_tone_mapper=1
anisotropic_filtering=1
shadow_resolution=0
gpu_device=1
volume=100
mute_in_background=0
audio_output=0
microphone=1
microphone_gain=100
fps_counter=1
fps_counter_position=0
fps_counter_size=0
version_and_hardware_at_every_level=0
vram_line=1
textures_line=1
draws_line=1
dispatches_line=1
render_passes_line=1
draws_skipped_line=1
texture_uploads_line=1
pipelines_built_line=1
gpu_slot_waits_line=1
queue_submits_line=1
cpu_and_gpu_lines=1
menu_size=2
game_speed=1
field_of_view=100
text_speed=0
text_size=0
skip_title_screen=0
menu_language=2
discord_status=0
skip_opening=0
controller_in_background=0
mouse_camera=0
disable_camera_centering=0
mouse_sensitivity=100
invert_mouse_vertical=0
invert_mouse_horizontal=0
invert_camera_x=0
invert_camera_y=0
camera_speed=100
stick_dead_zone=0
rumble_strength=100
motion_controls=1
motion_sensitivity_x=100
motion_sensitivity_y=100
invert_motion_x=0
invert_motion_y=0
motion_deadzone=1
layout_preset=0
button_prompts=0
walk_mode=0
walk_speed=45
menu_shortcut=2
controller_menu_button=1
compact_menu_key=0
nfc_tag=0
debug_tools=0
damage_taken=1
frame_pacing=0
threaded_rendering=0
descriptor_reuse=1
sampler_cache=0
robust_buffers=0
present_queue=0
astc_as_rgba8=0
intel_shader_compiles=0
intel_quick_compute_builds=1
memory_budget=3
gpu_device_id=(value left out)
auto_for=(value left out)
auto_tuned=(value left out)
auto_steps=(value left out)
options_version=6
Switches set (the environment and longshot_env.txt; a value only when it is a number or on/off, and never for a name with TOKEN, KEY, ROOM, SECRET, PASS, SERVER or USER in it):
LONGSHOT_NO_UPDATE_CHECK=1
Crash record: unclean-20261120T214539Z.txt
The end of longshot_log.txt
Its last 200 lines (the home folder written %USERPROFILE%, the user's name ):
Not in this report
Saves, game files, the game's executable and caches, memory dumps, keys, the options file itself and the path of your home folder.
Screenshots or video
No response
Before you send it
The end of this log shows Windows at its commit limit (RAM plus the page file) just before the game ended. There are eight
mem: commit of 0x10000 bytes at the commit limit made after ... mswaits, thenvk: a C++ allocation refused (at the commit limit?): tried again for up to 5 s. Then the log stops without a crash record, so the process ended inside one of the allocations that has no memory left to report with. With 16 GB of RAM the game, the driver and Windows need the page file to hold the rest.What should fix it for the reporter, @Ialago_Xeon: give the page file a fixed, larger starting size. Go to System Properties → Advanced → 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. Make sure that drive has the free space, and close browsers and other large programs while playing. #2078 (Market, an RTX 3060 Ti, 16 GB) is the same, and #1772 is the stack-overflow form of it (#1885).
If it still ends in Kakariko after that, please attach the whole
longshot_log.txtof that run.Posted by an AI agent (Claude Code) for d4nkn3ss.
Same failure as #1280: eight
mem: commit of 0x10000 bytes at the commit limit made after 50 mswaits, thenvk: a C++ allocation refused (at the commit limit?): tried again for up to 5 s, and the log ends with no crash record.f88e6e3a(#1291) covers this from v3.0.0-rc.7, with96caf2f2(#1885, nightly-695) and0d476e58(#2170, nightly-743) covering the stack and exception forms. fixed on nightly-745; this can be closed as a duplicate of #1280Correction 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.