Memory leak due to native error (from non secure uri)

[thomas-kl1]

\Magento\Store\Model\Store::isCurrentlySecure

$secureBaseUrl = $this->_config->getValue(self::XML_PATH_SECURE_BASE_URL, ScopeInterface::SCOPE_STORE);
$secureFrontend = $this->_config->getValue(self::XML_PATH_SECURE_IN_FRONTEND, ScopeInterface::SCOPE_STORE);

This methods tries to resolve the configuration from the current active store instead of the internal state ID of the object.
Passing the own object ID fix it:

$secureBaseUrl = $this->_config->getValue(self::XML_PATH_SECURE_BASE_URL, ScopeInterface::SCOPE_STORE, $this->getId());
$secureFrontend = $this->_config->getValue(self::XML_PATH_SECURE_IN_FRONTEND, ScopeInterface::SCOPE_STORE, $this->getId());

Because the scope ID is not passed by, Magento core try to resolve the current store ID, which is already what the system is currently trying to achieve.

magento/magento2#38717

[thomas-kl1]

Add check on

magento2-store-path-url/Plugin/App/Request/StorePathInfoValidator.php

Line 30 in 994cb7f

public function beforeGetValidStoreCode(Subject $subject, Http $request, string $pathInfo = ''): array

in order to prevent recursive call of the plugin.

[thomas-kl1]

Workaround: 67312b1

This change prevent the plugin to be called within the same stack of the parent plugin execution.
However it won't fix the Magento cire behavior, meaning that if your are coming from unsecure to secure, the core might be unable to resolve the current scope correctly (native behavior).