Skip to content

ImageSharp generates Fatal error. Internal CLR error. (0x80131506)  #2148

Description

@TonyValenti

Prerequisites

  • I have bought a Commercial License
  • I have written a descriptive issue title
  • 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.2

Other ImageSharp packages and versions

NA

Environment (Operating system, version and so on)

Windows 10, x64

.NET Framework version

6.0.5

Description

When publishing a ReadyToRun executable that uses ImageSharp, ImageSharp crashes the CLR.
Please see:
dotnet/runtime#70341 (comment)

Steps to Reproduce

Please see:
dotnet/runtime#70341 (comment)

Images

A single image is included in the project file attached to:
dotnet/runtime#70341 (comment)

Activity

  1. TonyValenti commented on Jun 9, 2022

    @TonyValenti
    Author

    Also, please note, this only affects executables published with ReadyToRun. "Regular" DEBUG and RELEASE executables work fine.

  2. brianpopow commented on Jun 9, 2022

    @brianpopow
    Collaborator

    This could be related to SixLabors/ImageSharp.Drawing#93

    The error message in ImageSharp.Drawing-Issue93 and the stack trace in .Net-Issue70341 both suggest that it has something to do with System.ValueTuple, but I am not sure how.

  3. brianpopow commented on Jun 9, 2022

    @brianpopow
    Collaborator

    @TonyValenti I am not sure what we can do about this issue. This looks for me like an upstream issue.

  4. JimBobSquarePants commented on Jun 9, 2022

    @JimBobSquarePants
    Member

    @TonyValenti I am not sure what we can do about this issue. This looks for me like an upstream issue.

    @TonyValenti has kindly already reported this upstream for us. Good to have a tracking issue I think for stuff like this despite us being unable to do much about it.

  5. JimBobSquarePants commented on Dec 8, 2022

    @JimBobSquarePants
    Member

    @TonyValenti It looks like the issue has been fixed upstream with .NET 7 so I'm going to close this now.

  6. TonyValenti commented on Dec 8, 2022

    @TonyValenti
    Author

    Thanks so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    upstream-issueIssue depends on upstream dependency fix.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions