corrupt JPEG data

  • Resolved Adendum

    (@adendum)


    9 years, 7 months ago

    In a website that has almost zero activity and has been using EWWW for the last 6-9 months without issue I am now seeing a bunch of errors in the log but have no idea what to look for to fix this….

    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 17 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 381 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 306 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 66 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 576 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 17 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:20:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 17 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 17 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 381 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 306 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 66 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 576 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 17 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907
    [08-Nov-2016 14:25:39 UTC] PHP Warning: getimagesize(): corrupt JPEG data: 17 extraneous bytes before marker in /home/drjl/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 907

    Do I have one or more corrupt images – if so how do I find and fix them as the site pages look OK to me.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Shane Bishop

    (@nosilver4u)

    9 years, 7 months ago

    There are a few possibilities besides corrupt JPGs, so let’s see what we can figure out. When you respond, please be sure to turn on EWWW’s debug option and post the debug information from the settings page via pastebin.com.

    My first thought is that getimagesize() is being run on a file that is not a JPG (like a PDF), and thus throwing that warning.

    The other possibilities are that you actually have corrupt JPG files, or that there is a bug in the getimagesize() function with whatever version of PHP you are using.

    However, the odd part is that those warnings all come within 1 second of each other, which makes me suspect that the files/images are being auto-generated somewhere, and that would almost certainly rule out the PDF theory, and the idea that you have corrupt JPGs.

    What we can try is to leave EWWW’s debug mode enabled for a couple hours, and then (along with the debug info from the settings page) look for the debug.log file in the ewww-image-optimizer folder. You can post that on a public sharing page (it might be too large for pastebin), or you can send it to me via https://ewww.io/contact-us/

    Thread Starter Adendum

    (@adendum)

    9 years, 7 months ago

    Hi,

    It just got ‘odder’!

    I deleted my error.log to replicate the issue – as it happens as soon as a browser gets the home page and the error is no longer happening. I think I may have fired one off prematurely here because I forgot that I also have my hosting engineers looking at an issue where I cannot update a theme translation file, and it transpires, I can’t install a plugin as both give “The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature”.

    So I think I should hold off doing anything right now. I’ll send you the debug file next but I suspect the problem is not with EWWW.

    Paul.

    Plugin Author Shane Bishop

    (@nosilver4u)

    9 years, 7 months ago

    Yikes, that sounds like a hardware issue of some sort, hopefully they can get it sorted quickly.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘corrupt JPEG data’ is closed to new replies.