Applications shouldn't abort while reading jpegs #3487
Labels
jpegli
Related to jpegli, also cjpegli and djpegli
unrelated to 1.0
Things that need not be done before the 1.0 version milestone
Describe the bug
I have noticed 0f0997c. Please don't make it into a release, jpegs are almost always untrusted input and aborting on them is a no-go. The commit message doesn't even explain why this is done... Lots of projects (at least Qt for sure) do setjmp/longjmp trick to recover from error_exit with libjpeg and its forks. The original libjpeg and its forks exit in the default error_exit handler, not after it.
The text was updated successfully, but these errors were encountered: