-
-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have 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
Improper call to JPEG library in state 201 #363
Comments
I am now working on a new release to resolve this issue. It has also been reported for ImageMagick and it was fixed there yesterday. A new release should be available in a couple hours. |
Ok. Great! |
this bug is still exsit in Magick.NET-Q8-AnyCPU 7.11.0 |
@284794507 can you attach an image that demonstrates this issue? |
https://github.com/284794507/.Net/blob/master/麦考瑞 - 副本.jpg |
I can't attach an image here. you can get it by that url. |
Improper call to JPEG library in state 201 `C:\Users**\麦考瑞 大尺寸.jpg' @ error/jpeg.c/JPEGErrorHandler/333 |
@284794507 I can open your image without any issues: using (var image = new MagickImage(@"I:\麦考瑞 - 副本.jpg"))
{
} Are you reading the file differently? p.s. There is an edit button for comments |
error code 在 ImageMagick.NativeInstance.CheckException(IntPtr exception, IntPtr result) |
|
Prerequisites
Description
Many JPG files will not read and give this error:
ImageMagick.MagickCorruptImageErrorException: 'Improper call to JPEG library in state 201 `[path to file]' @ error/jpeg.c/JPEGErrorHandler/333'
I have a number of examples but the files don't belong to me. If this is a definite bug and there is a way to get them to you securely that would be best.
I did testing with older Nuget versions all the way back to 7.1 or so and all of them have the same problem. Programs like Irfanview and MSPaint on Windows have no problem opening these.
--- EDIT: This only occurs on 7.9.1 ---
Steps to Reproduce
System Configuration
It's like an ImageMagick problem so let me know if it should be reported there.
The text was updated successfully, but these errors were encountered: