Mathieu De Zutter
Mathieu De Zutter
I agree. In general php pm should fail faster in order to be able to recover at all in some circumstances. In 10 seconds a lot can go wrong.
I'm having memory leaks after upgrading from doctrine-bundle 2.0.2 to 2.0.6. Workers reach max memory after 500 requests while the workers are only restarted after 1000 requests. I've downgraded it...
I agree this is an inherent problem, but the security consequences of this specific case are huge. I would check the session service after each request and if it's open,...
FYI, this is my workaround: ``` public function onFinishRequest(FinishRequestEvent $event): void { $request = $event->getRequest(); if ($request->hasSession() && $request->getSession()->isStarted()) { $this->logger->warning('Session not closed when processing request. Closing it now.'); $request->getSession()->save();...
After upgrade to Symfony 5.1, sessions are again leaking despite my workaround.
I'm still trying to figure out what causes the leak. The only way to reproduce it currently is to switch production to v5.1 and wait a few hours until it...
I'm back on 5.1 and the problem does not occur anymore. No way to reproduce it anymore. Still it would be a good thing if PHP PM were able to...
@tonyffrench When the json payload contains non-ascii characters, the calculated length of the payload is wrong. It counts the number of characters instead of the number of bytes. The result...
Same here. #97 fixes payloads with UTF-8.
@NeilPeyssard You're referencing this issue. You meant another issue?