Jump to content

PHP-FPM Signal 11 (SIGSEGV) with Tracy Debugger bluescreen


nloyola
 Share

Recommended Posts

I am using ProcessWire 3.0.242 on Debian bookworm, with PHP 8.3.14 and NGINX 1.22.1. I have TracyDebugger 4.26.45 enabled. 

Very recently, php-fpm reports a signal 11 when I have a PHP ParseError (or any other type of error). This causes NGINX to display a "502 Bad Gateway" page. If I disable Tracy Debugger, I see the Fatal Error screen in the browser. Does anyone know how to fix this problem?

This was not happening a few weeks ago. Before, I would see the Tracy Debugger bluescreen displaying the error.

I have tried the following but still have the problem:

  • increasing the Tracy Debugger "Reserved memory size"
  • disabling opcache
  • increasing the php-fpm memory limit
  • using previous versions of Tracy Debugger

Any help would be appreciated.

Thanks

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...