You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think that commit is the root cause. I can reproduce segfaults and "misaligned tcache chunk detected" even after reverting that commit. I'll check...
EDIT: I get crashes on 8.2 and 8.1 too.
EDIT: Although that might be unrelated...
My setup was broken, I can reproduce the issue with the session variables.
I managed to get a useful Valgrind trace:
==78794== Conditional jump or move depends on uninitialised value(s)
==78794== at 0x54191C2: php_session_cleanup_filename (session.c:126)
==78794== by 0x5419635: php_rshutdown_session_globals (session.c:162)
==78794== by 0x5427503: zm_deactivate_session (session.c:2809)
==78794== by 0x568C4C4: zend_deactivate_modules (zend_API.c:3196)
==78794== by 0x55AD8C0: php_request_shutdown (main.c:1841)
==78794== by 0x581373F: php_apache_request_dtor (sapi_apache2.c:562)
==78794== by 0x58142FA: php_handler (sapi_apache2.c:734)
==78794== by 0x1602A7: ap_run_handler (config.c:169)
==78794== by 0x1623A6: ap_invoke_handler (config.c:443)
==78794== by 0x18B716: ap_process_async_request (http_request.c:452)
==78794== by 0x180D54: UnknownInlinedFun (http_core.c:155)
==78794== by 0x180D54: ap_process_http_connection.lto_priv.0 (http_core.c:246)
==78794== by 0x175B17: ap_run_process_connection (connection.c:42)
In an MPM worker scenario we have 1 module, N threads. Each thread must
have their globals initialised. If we only initialise the filename
fields in MINIT, then the threads have an uninitialized value. If the
uninitialized value is not NULL, this leads to segfaults upon access.
Description
Hello,
Some of NixOS smoketests seems to have catched an issue with PHP 8.3.0 alpha 2, we are seeing a crash at the end of the requests:
According to my bisection, 180f785 seems to be the culprit.
PHP Version
PHP 8.3.0 alpha 2
Operating System
NixOS
The text was updated successfully, but these errors were encountered: