IE11 will not display PNG image

Not reproducible Issue #7553197

Details

Author
Angie K.
Created
May 13, 2016
Privacy
This issue is public.
Found in
  • Internet Explorer
Found in build #
11
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

  1. reference attached PNG image inside an HTML page via <img> tag.
  2. serve the page up in IE11.
  3. image will appear once.
  4. refresh page and image will disappear and will not render. Clearing cache does not help. Sometimes it will render again, but consistently will not render the file.
  5. IE displays a “DOM7009: Unable to decode image” warning in console.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

    • Thank you for the feedback. I have been unsuccessful reproducing this issue on the latest version of IE. I see you are testing this issue on 11.0.9600.18282, could you please update to 11.0.9600.18314  and test your sample and see if you can still repro. If you are able to repro despite the latest update could you please provide us your sample code and the information about your testing environment such as the OS build and version or virtual machine or physical machine etc. This will help our investigation.

      Best regards,
      The MS Edge Team

    • Could you tell me how to get that version of IE? I am not able to do windows updates due to admin controls on my machine. I downloaded https://www.microsoft.com/en-us/download/details.aspx?id=51917 and when I run this it tells me that “The update is not applicable to your computer.” I am running Windows 7 Enterprise/SP1.

    • You can install updates by enabling “Install new versions automatically” in about section of IE. You can also do this task in Control Panel\System and security\Windows Update and check for the updates or change update settings whichever is more convenient for you.

      Having said that, about the error you are getting I would suggest you to review the following page https://support.microsoft.com/en-us/kb/3057448
      On the other hand, as you mentioned that your system settings managed by your organization which could prevent you to perform certain system changes such as updates or any other system configurations. I would recommend you to communicate with your system admin regarding to this issue.

      Finally, some troubleshooting for the issue you have, I would suggest you to use another PNG file, to see if you can display it successfully, if yes then please try to open your failing image file in MS Paint and save as PNG again and see if this will fix the issue. If not as a temporary workaround for your issue, you can try to disable X-Content-Type-Options in your application. Before doing that please visit the following link for more details about MIME type security risks https://msdn.microsoft.com/en-us/library/gg622941(v=vs.85).aspx

      Best regards,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • As we have not received further information on how to repro
      this item of feedback - we will resolve it as not repro. Should you have the
      details needed in order for us to reproduce this problem in our test
      environments please feel free to reactivate this issue at your earliest
      convenience.

      All the best,

      The MS Edge Team

    • I may be able to add a few details to this issue:

      • It is specific for IE 11.0.9600.xxxxx (currently 18537) Windows 7, Server 2008R2 and 8.1
        ==> Tested on Windows 7 Professional SP1 x64 and x86 (updated)
      • It randomly occurs for most images but especially with large dimensions (e.g. >= 4500x3000)
      • The probability for getting the issue increases dramatically when switching multiple images (in an image viewer or similar).
      • The Issue occurs using local images and images requested from a server (ASP.Net app).
      • Once the issue occurs for an image, the image cache is (seems to be) overwritten and even previously correct renderings (another browser Tab/Window) will fail on reload.
      • When testing locally the file hash seems to matter more than the path, since once it occurs for an image it will occur even for different paths (containing this file).
      • It does not matter if the file header is correct or wrong.

      Changing the compatibility mode of the IE does not help nor does changing the X-Content-Type Options help to resolve the issue. The current release Version of IE11 on Windows 10 doesn’t run into the issue.

      Steps to reproduce:

      Note: As said before the issue is reproduce able on Windows 7 using the current IE11 release (I will check windows 8.1 later today).

      1. Simply use some picture viewer (locally or server based) e.g. https://fengyuanchen.github.io/viewerjs/ and add some large images (swap the sample images).
      • It will work with any number and type, but the issue will occur quicker using large images
      1. Execute the html/webpage in IE and switch the images a few times. It sometimes takes a while until the issue occurs and other times it occurs directly. It will however for almost any image file.

      I have tested files from around 2000x1500 350Kb to 10000x8000 15Mb and can reproduce it on different machines for all images even though (dimensional) smaller images tend to be rendered better than their larger counterparts.

      All images affected by the issue will be displayed as broke until the browser cache is cleared. IE will not try to reload them from the server, even when a time stamp is appended to the path or the “Always refresh from server” option is active in F12.

      Please come back to me, in case there are any problems reproducing the issue.

      Regards

      Max

    • on IE11.674.15063.0:
      We are running into this issue on a large webapp which has many images. Our 19 images totalling about 100MB cause this issue on random images each time we refresh. If we make IE load one of the images which was failing individually, it loads fine.

      This is very concerning to us as it is preventing a release to a client. It is disappointing that it was closed without investigation, and not re-opened when repo steps were added.

    You need to sign in to your Microsoft account to add a comment.

    Sign in