Sending images for optimization makes the site inaccessible

  • Resolved elaginnn

    (@elaginnn)


    2 years, 3 months ago

    Hi! When I send images manually for optimization, my site freezes. I see a CPU load of 100% , can’t remember about the memory load. The only thing that helps is renaming the plugin folder and clearing the .htaccess from the litespeed dereqs. I can’t do full tests as the site has to be online all the time. This may be due to incompatibility with WordPress version 6.1.1 ? Because I have not made any changes to the site, and the update may have been installed automatically.

    I discovered the problem when the Crop-Thumbnails plugin stopped working – images stopped being replaced in the post. Only turning off the Litespeed cache helped. This did not happen before. I went into picture optimization just in case and found a problem with manually sending for optimization. Could these problems be related?

    • This topic was modified 2 years, 3 months ago by elaginnn.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I am not aware of any change on image optm recently

    please try enable a debug log , see what does log say during that request

    and also please check , if you have access, on server , see which process(es) consume CPU

    best regards,

    Thread Starter elaginnn

    (@elaginnn)

    In general, sending images blocked resources on the hosting and none of my sites worked. There are basically only lsphp processes, 17 processes.

    I managed to deal with it by downgrading WordPress to 6.0.3, later I even rolled back to 6.0 . This prevents the blocking.

    But the problem with the image submission itself remains. I have a large unfinished queue of 1200 files, essentially no files coming back. As a result shows 100% optimized, but in fact they are not completed, resetting the incomplete does not help. And free limits are engaged. What could be the problem?

    What if I recreate thumbnails after optimization? How do I send them for optimization? This does not happen automatically.

    • This reply was modified 2 years, 3 months ago by elaginnn.
    • This reply was modified 2 years, 3 months ago by elaginnn.
    • This reply was modified 2 years, 3 months ago by elaginnn.
    Plugin Support qtwrk

    (@qtwrk)

    if you need to regenerate the thumbnails , it is better you destroy the optimized images first, then regenerate it , then re-optimize

    Thread Starter elaginnn

    (@elaginnn)

    OK, it helps in principle, but it’s not very convenient.
    There is a problem with the browser cache. If I did a crop, the browser will show the old version of the images (because their url hasn’t changed). Is there any way to correct this? There is some kind of check of cache actuality through headers, isn’t there? Is it configurable in the plugin?

    Plugin Support qtwrk

    (@qtwrk)

    well , as far as I know , there is no way you can flush browser cache from server side

    only possible way is to use new file name , or attach with query string , that’s why you see many js/css requests comes with query string , to control the version.

    Thread Starter elaginnn

    (@elaginnn)

    Thanks.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Sending images for optimization makes the site inaccessible’ is closed to new replies.