---

This section details on the original issue you should resolve

<issue_title>Currently forcing an infinite php memory_limit</issue_title>
<issue_description>## Bug Report

• Yes, I reviewed the contribution guidelines.
• Yes, more specifically, I reviewed the guidelines on how to write clear bug reports.

The Problem

WP CLI overrides server configurations and sets the memory limit to -1 during runtime, seen here:

wp-cli/php/WP_CLI/Runner.php

Lines 1276 to 1278 in c3bd5bd

	// Fix memory limit. See https://core.trac.wordpress.org/ticket/14889
	// phpcs:ignore WordPress.PHP.IniSet.memory_limit_Blacklisted -- This is perfectly fine for CLI usage.
	ini_set( 'memory_limit', -1 );

The mentioned trac ticket has been resolved for a while now :), and servers can configure -1 if they desire to.

Recommended Solution

I believe it would be best for WP CLI to remove itself from making this decision at run time. Setting proper memory limits allows for more graceful handling of requests/commands that do end up exceeding the limit. Otherwise, it can be left up to a lower-level process to kill off the request - leaving behind a less-than-graceful result (shutdown functions can't attempt to run, etc).

If it's agreed to remove this from the package, then I would recommend doing this in a major release with ample notice so others can decide on if they need to increase this value or not before upgrading.</issue_description>

Comments on the Issue (you are @copilot in this section)

@danielbachhuber @schlessera This seems like a good candidate for a 3.0.0 too.