alexp12

Solved, this was the root cause:

  The active child theme contained a global gettext filter that changed text on the WooCommerce My Account address endpoint:

  add_filter( 'gettext', function ( $translated, $text, $domain ) {
      if (
          is_admin()
          || ! function_exists( 'is_wc_endpoint_url' )
          || ! is_wc_endpoint_url( 'edit-address' )
      ) {
          return $translated;
      }

      // Translation customization...
  }, 20, 3 );

  This worked with WooCommerce 11.0.1. Under 11.1.0, calling is_wc_endpoint_url() during early translation initialization produced this recursive path:

  Child-theme gettext callback
    -> is_wc_endpoint_url()
    -> WC_Query::get_query_vars()
    -> woocommerce_get_query_vars filter
    -> OrderWithdrawalController::add_query_var()
    -> FeaturesUtil::feature_is_enabled()
    -> FeaturesController::init_feature_definitions()
    -> translation function / gettext
    -> child-theme gettext callback
    -> repeat

  WooCommerce 11.1.0’s Order Withdrawal controller adds logic to woocommerce_get_query_vars. Its feature check initializes the WooCommerce feature definitions, whose labels are translated. That invokes the theme’s gettext filter again before the original call has completed.

  The recursion continues until PHP exhausts its memory limit.

The theme callback was unsafe because it called a query-dependent conditional from gettext before the wp action. Adding the lifecycle guard fixes that theme behavior.

  However, WooCommerce 11.1.0 exposes the issue through a new recursive route involving OrderWithdrawalController, woocommerce_get_query_vars, feature initialization, and translation. Could WooCommerce consider adding a re-entrancy guard or avoiding translated feature initialization from  within the query-variable filter? That could prevent similar third-party translation callbacks from causing unbounded recursion and full-site HTTP 500 failures.

Applied workaround:

  The callback was changed so it does not query WooCommerce endpoints until WordPress has completed its main query:

  add_filter( 'gettext', function ( $translated, $text, $domain ) {

      if (

          is_admin()

          || ! did_action( 'wp' )

          || ! function_exists( 'is_wc_endpoint_url' )

          || ! is_wc_endpoint_url( 'edit-address' )

      ) {

          return $translated;

      }

      // Translation customization...

  }, 20, 3 );

  After applying this guard, WooCommerce 11.1.0 was installed successfully.