Beanstalk Longshot test farm
Menu

#1885 fix(mem): a thread's stack page refused at the commit limit waits for commit, then the thread goes on

by d4nkn3ss open Open on Forgejo

Commit

Head
3b1ad48
Base
main 2210931
Approval
can't be tested as asked: see the farm's comment

Plan (gpt-6.1-terra)

Not planned yet.

⚠️ Note: The recovery and persistent-out-of-memory branches cannot be reliably reached or judged without controlled memory pressure.

⚠️ Note: The farm cannot run the new standalone stack-commit fixture through a gameplay plan.

In plain words

The alternative plan loads a save and runs a minute of Hyrule Field gameplay on Windows AMD and Intel PCs, comparing main with the pull request. It takes about 12 minutes per tester and fails on a crash or a 15% increase in p99 frametime. No Intel tester is currently online, so that target will wait. No tester online now matches windows+intel: that target waits for one.

Asked for

Windows 10 and Windows 11, any GPU: with a small fixed page file (e.g. 2 GB on a 16 GB PC), load a save and teleport between Hyrule Field and the Market for a few minutes. Expect no 0xc00000fd crash; a "mem: a thread's stack grew at the commit limit after waiting" line means it recovered; if the PC stays out of memory, the out-of-memory notice shows before the game closes. Also a normal start on Windows AMD and Intel: play a minute, expect it to play and close as on main.

can't test this as asked: The requested Windows 10 and 11 commit-limit test requires a fixed small page file or a per-process commit limit, neither of which the farm can configure; it also cannot target Windows versions separately or verify the out-of-memory notice. The alternative can check normal Windows gameplay on AMD and Intel, but cannot establish stack recovery at the commit limit.

Targets

The plan has no targets yet.

Reports

No reports yet. Each tester posts one when its job ends.

Jobs

No jobs. Jobs are made once the plan is approved.