Bug #83786


Wrong Token Crashes Server

Added by John Miller over 6 years ago. Updated over 6 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


TYPO3 9.2

OS: Windows 8.1
Server: Apache 2.4.29
PHP: 7.2.2
MySQL: 5.6.35

Just discovered that when you apply the wrong backend token, the server stops and restarts. Sometimes the wrong token comes into effect when one navigates back to earlier pages with a different token in the backend.

1) Login into the backend.
2) Add a number to the token on the address bar on the browser.
3) Press enter.
4) You'll be notified of an invalid token.
5) Check the Apache error log. You'll see something similar to "Parent: child process 832 exited with status 3221226356 -- Restarting."

Actions #1

Updated by John Miller over 6 years ago

  • Target version changed from 9.1 to 9.2
Actions #2

Updated by Christian Kuhn over 6 years ago

  • Status changed from New to Closed

Hmm, that sounds more like a server / apache / php process / mod php / fpm issue. Something in this area. If the userspace php code is able to crash apache, that is not the fault of the application but somewhere in php or apache or their gameplay, or their setup.

I fear there is little we can do about that, if you want to track that down, you maybe could reduce the offending code lines down to a little script and then play around with that or ask for help - maybe in PHP community.

I'll close the issue since I don't know how we could be of significant help here.

Actions #3

Updated by Oliver Hader over 6 years ago

That rather sounds like a general PHP & Apache problem...

  • how is PHP used in Apache (fcgid, mod_php, ...)?
  • what's the multi processing module (MPM) being used in Apache?
  • are other Apache modules involved in handling request & response - e.g. proxy or ssl?
Actions #4

Updated by John Miller over 6 years ago

- PHP is using mod_php (mod_php7)
- Multiprocessing module is obviously mpm_winnt (Windows) with adjusted threadsize
- Other Apache modules involved in handling such as proxy, ssl? None.

You are right. Thanks for the heads up. Just went through the entire configuration files for Apache (all of them -
line by line) and found that I had not set the stack size (ThreadStackSize) as recommended. Just set it to 16 Mb (16777216). Everything else is fine. Now works well and fast.

Am very grateful to both of you for the suggestions. Will leave this answer here for anyone that might find it useful in the future.


Also available in: Atom PDF