As per doc, "logging" is set to %kernel.debug% by default, which creates memory leaks in consumers and long-living commands with debug enabled. The leakage itself is in MessageLogger plugin that only appends messages. The details are here. I wonder if there is any solution already? We could find a way to distinguish a long living process/command and set "logging" from a variable.
As per doc, "logging" is set to %kernel.debug% by default, which creates memory leaks in consumers and long-living commands with debug enabled. The leakage itself is in MessageLogger plugin that only appends messages. The details are here. I wonder if there is any solution already? We could find a way to distinguish a long living process/command and set "logging" from a variable.