Phalcon C-Extension and PHP Zend API Version Interoperability

Phalcon operates as a compiled C-extension, meaning it is loaded directly into the PHP process memory. This architecture creates a strict dependency between the framework binary and the specific Zend API version of the installed PHP runtime.

When upgrading the environment, there is a risk of binary mismatch. Because the extension is loaded at process start, an incompatible version can trigger a segmentation fault, leading to a total PHP process crash rather than a catchable PHP exception.

Given that Phalcon cannot be managed via standard user-land version control, the boundary between the compiled .so/.dll file and the PHP-FPM process requires precise alignment.

• What is the documented behavior for detecting a Zend API mismatch before the PHP process attempts to execute the extension?
• Are there specific configuration parameters in phalcon.ini that can mitigate process crashes during a version mismatch?