Skip to content

test: keep the out-of-memory query under the hard limit in worker mode - #2778

Merged
dunglas merged 1 commit into
mainfrom
test/oom-worker-hard-limit
Oct 26, 2026
Merged

dunglas merged 1 commit into
mainfrom
test/oom-worker-hard-limit

Conversation

@dunglas

@dunglas dunglas commented Oct 26, 2026

Copy link
Copy Markdown
Member

TestOutOfMemory_worker kills the test binary in the Docker images (Hard memory limit of 16777216 bytes exhausted), on every variant. It also fails on main, but Docker tests only run on PRs labeled "CI: All jobs", and none ran since #2741 introduced the test.

Worker mode holds four copies of the query string while populating the superglobals, so the 5 MiB query crosses the 16 MiB hard limit (twice memory_limit). The Tests workflow's PHP build stays just under it.

3 MiB still crosses memory_limit, which the test asserts, and stays under the hard limit: 4 MiB still exits, 2 MiB leaves little margin above memory_limit. Passed 20 times in a row in the Trixie builder image (plus 5 with -race), and with a local PHP 8.5 build.

Unblocks #2777.

Worker mode holds four copies of the query string while populating the
superglobals, so a 5 MiB query crossed the 16 MiB hard limit on the
official PHP images and killed the test binary.
@dunglas
dunglas merged commit 922eb4b into main Oct 26, 2026
43 checks passed
@dunglas
dunglas deleted the test/oom-worker-hard-limit branch October 26, 2026 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant