You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
That PR only clarified the current status.
Generally, we are moving towards removing aborts in JXL library; likely we will be able to do so for JPEGLI as well.
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: