| 3 | | The reason that the update from [https://core.trac.wordpress.org/changeset/55404] caused this breakage is that the Imagick timeout setting begins counting from its first instantiation within the PHP process. As we know, many server configurations are setup to spawn a few PHP processes and reuse them over many requests, only spawning new processes when needed. So, by forcing the Imagick timeout value to align with the PHP timeout value, after a couple of requests, you're effectively setting the Imagick timeout to a value that has already elapsed, which then times out, causing that PHP process to exit. The server will replace that PHP process with a new one, starting the whole process over again. |
| | 3 | The reason that the update from [55404] caused this breakage is that the Imagick timeout setting begins counting from its first instantiation within the PHP process. As we know, many server configurations are setup to spawn a few PHP processes and reuse them over many requests, only spawning new processes when needed. So, by forcing the Imagick timeout value to align with the PHP timeout value, after a couple of requests, you're effectively setting the Imagick timeout to a value that has already elapsed, which then times out, causing that PHP process to exit. The server will replace that PHP process with a new one, starting the whole process over again. |