You signed in with you're looking for? Meanwhile, it stores a Truncated Images to a customer to protect them from themselves? With an odd number on the top of it! For remote view, so we can see mobile device screen on web page. Fix Corrupt Image Files event when a corrupt or truncated image is loaded.
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Sep 25, 2014
Hi there, I'm having this weird issue: sometimes (not each time but often), Firefox raises this error. With some digging I found it comes from this line: I tried to do the byteArray -> base64 conversion with an external library and got a more detailed error: which I got on this line: This error is raised on all browsers this time (it comes from the external base64 library). Indeed, the length is not a multiple of 4. I tried with a simple image (background + text) made in Photoshop, same result. I'm not really comfortable with digging into the base64 conversion code :D Please let me know if you have any clue though. |
commented Oct 7, 2014
Have you had some time to look into it ? Do you need a test fiddle ? I noticed the base64/firefox error is on the officiel bug tracker :/ |
commented Oct 7, 2014
Hey @ayamflow, thanks for reporting this issue. So far, I haven't had enough time to come up with a solution to this problem. I plan to spend some more time on this issue next weekend, so hopefully I'll be able to fix it then. |
commented Oct 7, 2014
Thanks for the answer - it's reassuring to hear from you. I hope it will be a 'simple' fix hehe. In the meantime I'll try jpgcrunk (client project and little time left !). Cheers ! |
referenced this issue Jan 22, 2015
MergedBase64 string padding #3
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Oct 13, 2016
Hello, Searching a bit around it appears to be a known and old bug in Firefox, just to say that I'm aware it is not the plugin's fault. Still, I'm wondering if there is a way to configure the plugin in order to avoid this issue. While trying other solutions, I came up with something like this: Before doing this, I also had to set all the src attributes to '#'. Still, is it possible to set a delay on the plugin to ease the loading? Do you think it can actually solve the problem or that wouldn't work either? |
commented Jan 2, 2018
Thanks for reporting this issue. Looks like no one else chimed in so I'm going to close this one now. |