- Issue created by @pauger
- Status changed to Needs review
about 1 year ago 9:27am 10 November 2023 - π«π·France ckhalilo
This patch is working for me.
Without this patch in my env PHP 8.2, I have 200% CPU and Memory limits is reaching more 190%.Thank you.
- Status changed to RTBC
12 months ago 5:36pm 29 December 2023 - πΊπΈUnited States Chris Burge
I just had a customer run into this. Immediately upon upgrading to Drupal 10.1.7, we observed CPU maxed out at 100%, which crashed their hosting stack. The following errors were showing up in the logs:
[20-Dec-2023 12:08:07 America/Los_Angeles] PHP Fatal error: Maximum execution time of 300 seconds exceeded in /mnt/www/html/[omitted]/docroot/modules/contrib/az_blob_fs/src/StreamWrapper/AzBlobFsStream.php on line 592 request_id="v-c9248472-9f72-11ee-9656-cb202b0e421b"
[20-Dec-2023 14:38:51 America/Los_Angeles] PHP Fatal error: Maximum execution time of 300 seconds exceeded in /mnt/www/html/[omitted]/docroot/modules/contrib/az_blob_fs/src/StreamWrapper/AzBlobFsStream.php on line 410 request_id="v-d824acee-9f87-11ee-a31c-4bdba48a437c"
Since the method checking end of file never returns true, it looks like the process just hangs until it eventually times out at 300 seconds (5 minutes). That can quickly lead to proc exhaustion.
Following deployment of patch #2, the errors ceased and application performance returned to normal.
I'm also upgrading the status to critical since this bug has been observed causing application downtime.