Expected result:
----------------
run complete.

Actual result:
--------------
crash.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.

if set 
opcache.jit_buffer_size=512M
opcache.jit=tracing

then crash.

if 
opcache.jit_buffer_size=512M
opcache.jit=function 

will not crash.

but I can't give more info.
who can help?

ubuntu sys log report:

ool www: DIGEST-MD5 common mech free

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.

(gdb) bt
#0  0x000055fabc84a595 in ?? ()
#1  0x2020200020202020 in ?? ()
#2  0x0000000000000023 in ?? ()
#3  0x0000000000000000 in ?? ()



why ??

open

Thanks for the swift reply!  However, the backtrace is useless,
but I should have expected that because this is a JIT issue.

What SAPI do you use?  FPM or (F)CGI?  If the latter, that would
likely be a duplicate of bug #81679.

I use php-fpm

open

> I use php-fpm

Okay, then it may have a different root cause.

Hi,

Not 100% sure if my comment is related, but I have reasons to think it is so I'll post it (basically, the logs says core dump as well).

I am also using PHP8.1, Laravel 8 along with NGINX 1.21/1.19 (tested on both), and php-fpm using opcache and JIT tracing. I am using docker and docker swarm to serve this project. Also, my nginx and php containers have a health check that waits for a "service nginx status" (NGINX) and a custom laravel command for the php-fpm container.

My problem is similar, but not quite the same : it does not happens every time I start the containers, sometimes it works fine, sometimes the bug occurs, I'd say it happens about 50% of the time... Seems like this bug is a tough nut

When this bug happens, my php-fpm containers are turning crazy, returning HTTP 509 and printing the following output in loop : 
WARNING: [pool www] child 10366 exited on signal 11 (SIGSEGV - core dumped) after XXXXX seconds from start 

Some requests are served, some are HTTP 509, and the warning is returned every seconds in the logs.
Strange thing that might helps : during this episode, I also had the following output printed twice in the logs :
WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 1 idle, and 22 total children

Strange thing is that 22 children wasn't my max_children defined in the config, here is my config :

clear_env = no
pm = dynamic
pm.max_children = 50
pm.start_servers = 10
pm.min_spare_servers = 10
pm.max_spare_servers = 15
pm.max_requests = 600

When this bug happens, I have to shutdown the containers, and start them up again until it disappears (sometimes I need to restart the containers twice in a row). When the bug is not there, everything works fine though, my whole project have no issues.

Hope this helps you to find the origin of this bug.

Regards,

I run the ab -n 10000 -c 100 -k 'http://www.laravel9.com'

the crash.

If I open the http://www.laravel9.com first in browser,
nest step  run the ab -n 10000 -c 100 -k 'http://www.laravel9.com',
then will not crash.

I run the ab -n 10000 -c 100 -k 'http://www.laravel9.com'

then crash.

If I open the http://www.laravel9.com first in browser,
next step  run the ab -n 10000 -c 100 -k 'http://www.laravel9.com',
then will not crash.

How to install that "laravel9  echo  hello world"?

install laravel9:

composer create-project laravel/laravel example-app "dev-master"

then in the routes/web.php

write:
Route::get('/', function () {
    return 'hello world';
    
});

I feel that this is also related to, or a duplicate of, https://github.com/php/php-src/issues/8461

php8.1.8 fixed this problem.