docs(worklist): row 5.6 measured on main on Windows: the commit settles at ~20 GB and does not grow over a second lap #995
No reviewers
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!995
Loading…
Reference in a new issue
No description provided.
Delete branch "d4nkn3ss/Longshot:docs/worklist-memory-measured"
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?
Type: docs · Risk: low · Tested on: Windows 11, RTX 3080 · Needs: none
Why
Worklist row 5.6 (memory fills up over play time, the top row) still says "Next: retest on the next release". There was no measurement of main on Windows, where most of its reporters play. Two runs today give one: on a 10 GB card with 64 GB of RAM the game's commit settles at ~20 GB and doesn't grow over a second lap. The row should say so, say what the 20 GB is made of, and name the runs it still needs: a 16 GB PC and a 6-8 GB card, which this PC can't stand in for. See #388, #939, #992.
What changed
Row 5.6 gets the measurement and its next step. The two runs are files in
docs/tested/.docs/worklist.mdrow 5.6: "Next: retest on the next release ..." now reads "Measured on maina8a30c22...". It gives the split (guest window 7.6 GB, VRAM blocks charged to the commit 7.4-8.1 GB, the rest 4.3 GB), the Nov 14 build's growth, the open issues and PRs on it (#388, #939, #992), and a next step: a memtour run from a 16 GB Windows PC and from a 6-8 GB card, plus the reporters' logs. Score, owner and links are unchanged.docs/tested/2026-11-15-memtour-windows-d4nkn3ss-main.mdand...-dc390e59.md: the two runs, one row each.Measurements
Verdict: nothing to measure for this change, which is docs only. The runs it records are the measurement: main @ a8a30c22's commit is 20,355 MB after lap 1 and 20,035 MB after lap 2, while dc390e59's "rest" grew by about 440 MB over lap 2. Method and log lines are on #992 (comment).
Flags and settings
None
Testing
Tested:
python -I -B tests/test_tested_configurations.py: the two new files pass its format checks. Its one failure,test_cli_ascii_pipe_emits_the_arrow_containing_source_as_utf8(CRLF against LF on Windows), fails on main too.python -I -B tests/run_all.pyfrom PowerShell on Windows 11, with llvm-mingw from the Longshot Builder: 596 passed, 18 failed, 42 skipped on this PR @ 936bfc24 (rebased on main @bbe421f5since, with the crashes' sentence added:a0b90618; before that oncefce0d1:9351bdb1, docs only). All 18 fail on main @a0be15b3too:test_auto_handheld,test_crash_dialog,test_crt_options,test_fsr_uniform_ownership,test_guest_imported,test_import_reach,test_linux_preflight,test_make_game_cache,test_missing_nup,test_pads_after_menu,test_parallel_init_order,test_pending_guest_import,test_release,test_replay_write_order,test_run_all_changed,test_tested_configurations,test_vk_occlusion_queriesandtest_walk_key. Three are fixed by #993,test_releaseby #144 andtest_run_all_changedby #954.Not tested: the website's catalogue build. The files follow
docs/tested/README.mdand its check.Must be tested: None. The change is to docs only.
Risks
What could break: nothing: two new files and one table cell.
Turning it off: revert the commit.
Compatibility: Nothing changes.
Issues
See #388, #939
Checklist
Everyone
type(scope): description) of the status line's type.main.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named).third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.docs/tested/for each new measured run (format indocs/tested-configurations.md).🤖 Generated with Claude Code
WIP: docs(worklist): row 5.6 measured on main on Windows: the commit settles at ~20 GB and does not grow over a second lapto docs(worklist): row 5.6 measured on main on Windows: the commit settles at ~20 GB and does not grow over a second lapbibiburl referenced this pull request2026-11-16 05:15:24 +00:00
9351bdb116a0b90618f2Rebased on main @
bbe421f5(nowa0b90618), and row 5.6 now also names the crashes at the commit limit: six reports with an uncaught C++ exception (0x20474343) after their logs reached Windows' commit limit, which #1056 makes the crash window call out of memory.test_doc_anchorsandtest_tested_configurations' format checks pass on the two run files as before. The latter's Windows CRLF case still fails, as on main (#493).Posted by an AI agent (Claude Code) for d4nkn3ss.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.