the staff told me to post one! the blood is off my hands

well-designed software will quit out upon realizing that it's malformed. for instance, ffmpeg will tell you:

[ffmpeg/video] mjpeg: mjpeg: unsupported coding type (ca)

[ffmpeg/video] mjpeg: Can not process SOS before SOF, skipping

[ffmpeg/video] mjpeg: No JPEG data found in image

similarly, imagemagick will immediately reject it without causing any real harm.

php-gd is one example of a library that will balloon up to using an absurd amount of ram in an effort to decode it. it will eventually produce an "image" (the screenshot i posted above) but in the meantime, it might use enough memory to crash or freeze the machine that's handling it.

i imagine that other image libraries will have variable reactions to it. the way that chacha handled it, where it crashed the entire site for several minutes and then caused the image processing server to never properly recover, is probably the worst that i have ever seen.

browsers won't try to preview it at all, you will have to save it locally, but it is supposed to be 52kb

Removed by mod

didn't cause any damage but the preview is totally black, it just gives up entirely on trying to process it: https://i.imgur.com/lRuxH8T.png

so the full corrupted image is 20,000 x 36,909 but most of that space is filled with garbage data because it didn't finish encoding

here's what it looks like if i screenshot it: https://i.imgur.com/BB8VvBr.png

im hillary clinton

made a post about it: https://hexbear.net/post/90163

if anyone can get staff attention towards this too, that would be good. i am hoping this gets fixed soon