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.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.

I will not have time soon to test in debug mode
But I will do it someday :)

Doesn't reproduce on built-in server at least.

With FPM I do see a "502 bad gateway", though no actual crash.

I'm facing the same issue while trying to send extra one cookie using the code 

setcookie('GLSU', $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'], 0, '/' , $_SERVER['SERVER_NAME'], true, true);

When I commented out one of the cookies (other, not this), all works fine.
No 'buben-dances' helped to solve the issue, not changing the cookie data, nor cookie name or any other credentials. It looks like only cookie count matters.

If needed, I'm ready to help to reproduce it.

Thank you for the comments, I am happy to see someone also has the same issue

> If needed, I'm ready to help to reproduce it.

Please go ahead

> With FPM I do see a "502 bad gateway", though no actual crash.

I called this a crash because I assumed that is the case or a response would be sent if the process did end normally

I have Debian 9 + Nginx + PHP-FPM(7.2)
What else info do you need?
Please, ask direct questions or give me instructions what to do to help you.

Is the 502 coming from nginx or php-fpm?

The 502 is coming from php-fpm (php-fpm is crashing)?
After a long time debug i've found that issue is coming from the method of deleting a cookie.
In my project i need to update cookie domain from parent to child. To do this, i previously delete the cookie, and on the next line set it again with the new credentials.
Non-working code is:
     setcookie('COOKIENAME', '', 0, '/', 'myhost.com', true, false);
     setcookie('COOKIENAME', 'COOKIEVALUE', 0, '/', 'sub.myhost.com', true, false);

I've found that while i'm deleting a cookie, there is no need to set any additional data, but only name, value and zero-time. Any additional credentials are cause the 502 error. Also, no cookie-name or cookie-value matters.

Working code is:
    setcookie('COOKIENAME', '', 0);
    setcookie('COOKIENAME', 'COOKIEVALUE', 0, '/', 'sub.myhost.com', true, false);

Hope, it will help.

Hi,

Could someone have a look into this one ?, I still reproduce it.

nikic@php.net maybe ?

Regards

I just checked this again. Running FPM behind nginx and the provided test script, I see

2020/08/11 10:51:42 [error] 82419#82419: *2 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET /test.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "localhost"

messages in the error log. After adding

		fastcgi_buffers 16 16k; 
		fastcgi_buffer_size 32k;

to my nginx config, it works fine.

So this looks like a server configuration issue to me. Your web server rejects the massive HTTP header you are sending.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.