Increase Playground runtime PHP memory_limit to 512M - #3936
Merged
Conversation
…ory-limit' into stu-1821-increase-playground-memory-limit
gcsecsey
marked this pull request as ready for review
June 23, 2026 16:05
gavande1
approved these changes
Jun 24, 2026
Member
Author
Thanks! Yes, I think the setup I used was pretty reasonable. A normal Woo site would also have this many plugins and might hit local memory limits. The original reporter also hit the memory limit when cloning their site to Studio. Also, just as a side note, raising the limit to 512M for Playground is matching the limit we already have in place for native PHP. |
gcsecsey
enabled auto-merge (squash)
June 24, 2026 15:58
gcsecsey
disabled auto-merge
June 24, 2026 19:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
This PR addresses "Problem 2 (fatal errors / memory exhaustion)" from that report.
How AI was used in this PR
Used Claude Code to reproduce the wp-admin OOM locally, trace it to the Playground runtime's memory cap, and verify the fix against a heavy plugin stack.
Proposed Changes
The reported issue is that when a site with numerous plugins is cloned into Studio, and then run with the Playground runtime, the front-end loads but wp-admin dies with
Fatal error: Allowed memory size of 268435456 bytes exhausted(256 MB).The PHP-WASM HTTP server serves every request with a hard-coded PHP
memory_limitof 256 MB. A realistic production plugin stack (WooCommerce, WooPayments, Jetpack, Jetpack Boost, Jetpack CRM, MailPoet, Site Kit, etc.) already peaks at ~224 MB on an empty database, so wp-admin tips over 256 MB when the site's plugins and data load.This PR raises the Playground serving
memory_limitto 512 MB, matching the native runtime, so the two behave consistently, and heavier sites can open wp-admin.Testing Instructions
Pre-merge Checklist
npm run typecheckpasses; eslint clean on the changed file.)