2026-10-22 11:01 UTC
@GossiTheDog@cyberplace.social There's a lot more setjmp/longjmp use in there, which would make it even harder to reason about the code than normal for a project like this. Combine that with trying to handle out of memory conditions without terminating, and I wouldn't be surprised if there are a lot more bugs out there.
I can understand why you wouldn't want mod_php taking down the web server in these cases, but perhaps that just means putting the language runtime inside the web server is a bad idea.
Replies (1)
-
@gvenema@fairmove.net 2026-10-22 13:00
@jamesh@aus.social @GossiTheDog@cyberplace.social I call dibs on this. See my comments here at line 573. I also ran into longjmp problems and solved them also. Unfortunately the PHP team only wanted a quick oneline fix of the handler which later bit them again on pipelined http requests. https://github.com/gmoniker/php-apache2handler/commit/11aa93f85afcf837fd299b3557191f00cc026ec9