Possible memory leak?

  • Resolved jamieburchell

    (@jamieburchell)


    5 months ago

    After running the manual optimisation over approx. 200 images I noticed that all of my PHP-FPM threads had a much higher memory usage than before. Unfortunately, the memory usage then does not come down until the process is restarted. The pool is configured to use a static amount of threads and will cycle them after 1000 requests. I’m not sure if this is expected, or if there could be a memory leak in the code?

    The clearing and destroying of the image should probably be added to the Exception handler in CompressX_Image_Opt_Method::compress_image_imagick_ex, but I don’t think this is the cause.

    Also, while looking at the code I spotted this a couple of times – I think the error message should be “not support imagick” ?

    if(!CompressX_Image_Opt_Method::is_support_imagick())
    {
      $ret['result']='failed';
      $ret['error']='not support gd';
      return $ret;
    }
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support tonyrobins

    (@tonyrobins)

    Hello @jamieburchell

    Thanks for your feedback.

    We are going to take a look at the issue and get back to you as soon as we can.

    All the best,

    Thread Starter jamieburchell

    (@jamieburchell)

    Thanks!

    Plugin Support tonyrobins

    (@tonyrobins)

    Hi @jamieburchell

    If the optimization was completed normally, it should not enter the Exception handler position, so it should not be the problem.

    We’ve also checked the plugin code but find nothing abnormal, but we are definitely going to keep an eye on the issue.

    Regarding the error message, you are right, we are going to fix it in the next public release.

    Again, thanks for your feedback and information.

    All the best,

    Thread Starter jamieburchell

    (@jamieburchell)

    Thank you for checking!

    I have just tested a competitor/alternative plugin and the memory fluctuates and ultimately remains quite a bit higher, so I suspect this is to be expected with memory intensive operations.

    Plugin Support tonyrobins

    (@tonyrobins)

    @jamieburchell

    You are welcome.

    Please let us know if you need any further information or assistance using the plugin.

    All the best,

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.