[wp-trac] [WordPress Trac] #58202: php-fpm7.4: time limit exceeded `Operation canceled' @ fatal/cache.c/GetImagePixelCache/1868.

[WordPress Trac]

#58202: php-fpm7.4: time limit exceeded `Operation canceled' @
fatal/cache.c/GetImagePixelCache/1868.
--------------------------+-----------------------
 Reporter:  dsar          |       Owner:  antpb
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  6.2.3
Component:  Media         |     Version:  6.2
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------

Comment (by azaozz):

 Replying to [comment:21 mikeschroder]:

 Yes, will revert in few min.

 > It seems like because it's a public method, the route would be to remove
 setting the time limit by default, but leave the ability to do so?

 Yea, sounds reasonable. Although thinking it may also be good to deprecate
 `set_imagick_time_limit()` and even maybe "disable" it (just trigger
 deprecation notice and return). The the default
 [https://github.com/ImageMagick/ImageMagick/blob/a8de149e1aca79836319b31c8881537115e478ff/MagickCore/resource.c#L1283C70-L1283C70
 processing time limit] in ImageMagick is "infinity". Don't see why WP
 should be changing that or even have a method to change it.

 I'll just commit the deprecation for now, but lets remove the
 functionality if all agree.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58202#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform