Uncaught (in promise) DOMException: The source image cannot be decoded.
See original GitHub issueUncaught (in promise) DOMException: The source image cannot be decoded.
Any idea why? It works for other images.
Thank you for making this JavaScript script.
I am using the yall-2.0.1.min.js file.
Issue Analytics
- State:
- Created 5 years ago
- Comments:19 (11 by maintainers)
Top Results From Across the Web
DOMException: The source image could not be decoded
As a first step, you can check if the file signature matches one of the JPEG image: new Uint8Array( (await blob.slice(0,3).arrayBuffer()) ).join ...
Read more >Smart slider Bug Console (DOMException: The source image ...
This error message usually occurs when you reach a browser limitation so the browser will refuse to load and decode the image. People...
Read more >The source image could not be decoded when loading high ...
Hi there, I'm trying to load multiple objects using the GLTF loader with high resolution textures (8192 x 8192). All the models load...
Read more >createImageBitmap() reports "source image could not be ...
Issue 979890: createImageBitmap() reports "source image could not be decoded" but works in Firefox and as <img> · 1. No error should be...
Read more >The source image cannot be decoded, try again later - Reddit
The source image cannot be decoded, try again later. All my designs are procesed and saved in the same way with Photoshop. Thanks...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you for merging that in.
I think you are right about removing image decode. I saw this: “Decoding of large images can block the main thread for hundreds of milliseconds or more, interrupting fluid animations and user interaction. Currently, there’s no way for a web author to specify that they want an image to be decoded asynchronously, so there are scenarios where it is impossible to avoid UI stalls.” https://github.com/whatwg/html/issues/1920
I’m sorry you’re having this kind of trouble. It’s starting to make me wonder if async decoding is worth the trouble. 🤕
If at any point you could share the code, let me know. I haven’t received this error, but just because no one else has said anything doesn’t make me think this isn’t a potential problem.
I’ll keep this issue open for the foreseeable future in case anyone else is having trouble. In the meantime, try this unofficial build which removes async image decoding: yall-2.0.3.min.js.zip
Best of luck!