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
I have verified that I am running the latest version of ImageSharp
I have verified if the problem exist in both DEBUG and RELEASE mode
I have searched open and closed issues to ensure it has not already been reported
ImageSharp version
2.1.0
Other ImageSharp packages and versions
none
Environment (Operating system, version and so on)
Windows 2016
.NET Framework version
6.0
Description
We have an ASP.NET 6 app that uses ImageSharp 2.1 to resize images and create thumbnails (and that's it) for UGC. Several times a day, during high-load, our app crashes with this error:
Application: w3wp.exe
CoreCLR Version: 6.0.322.12309
.NET Version: 6.0.3
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF932A2A5A9 (00007FF932940000) with exit code 80131506.
It's very simple code. But this uncatchable error crashes our entire process.
Reverting back to 1.0.4 seems to help.
Steps to Reproduce
Unfortunately I'm unable to reliably tell which images caused this, since it's a busy app with millions of HTTP requests. Also I had no time to create process dumps or anything, But I did narrow this down to ImageSharp - reverting nuget from 2.1 to 1.0.4 fixed the issue immediately. So I thought you should know.
PS. Also, posting this is to help someone who's going to google for a solution desperately
Prerequisites
DEBUGandRELEASEmodeImageSharp version
2.1.0
Other ImageSharp packages and versions
none
Environment (Operating system, version and so on)
Windows 2016
.NET Framework version
6.0
Description
We have an ASP.NET 6 app that uses ImageSharp 2.1 to resize images and create thumbnails (and that's it) for UGC. Several times a day, during high-load, our app crashes with this error:
It's very simple code. But this uncatchable error crashes our entire process.
Reverting back to 1.0.4 seems to help.
Steps to Reproduce
Unfortunately I'm unable to reliably tell which images caused this, since it's a busy app with millions of HTTP requests. Also I had no time to create process dumps or anything, But I did narrow this down to ImageSharp - reverting nuget from 2.1 to 1.0.4 fixed the issue immediately. So I thought you should know.
PS. Also, posting this is to help someone who's going to google for a solution desperately
Images
No response