Access Violation Exception from UnpackToRgbPlanesAvx2Reduce · Issue #3104 · SixLabors/ImageSharp · GitHub
Skip to content

Access Violation Exception from UnpackToRgbPlanesAvx2Reduce #3104

Closed

Description

@SunaeK

Prerequisites

  • 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

3.1.11

Other ImageSharp packages and versions

.

Environment (Operating system, version and so on)

Windows

.NET Framework version

8.0

Description

AVE From UnpackToRgbPlanesAvx2Reduce.txt

When using our tool with SaveAsJpeg in ImageSharp, I got this AVE error (see attached error log) for certain images.
Changing the method to SaveAsPng resolved the issue.

Also for color images with a pixel count not divisible by 8 and less than 3 pixels over, a padded copy is created to avoid JPEG encoding issues as a work-around.

Steps to Reproduce

When I checked individual images with the SaveAsJpeg method using a few commands, this was fine, so at this point I am not sure.

Images

Images to send.zip

Activity

  1. JimBobSquarePants commented on Apr 7, 2026

    @JimBobSquarePants
    Member

    @SunaeK Are you able to create a minimal code sample to replicate the issue? I cannot do much without one.

    Update. Actually, I think I can see the issue in the code. PR opened.

  2. added a commit that references this issue on Apr 7, 2026
    e06a015
  3. SunaeK commented on Apr 8, 2026

    @SunaeK
    Author

    Thank you!

  4. sandorkerekes commented on Sep 15, 2026

    @sandorkerekes

    Hi there,

    We're hitting this on ImageSharp 3.1.12 in production (Umbraco 13, ImageSharp.Web, Azure App Service, .NET 8) — same UnpackToRgbPlanesAvx2Reduce frame, fatal process crash. The backport in #3106 is merged to release/3.1.x but there's no 3.1.13 on NuGet. Umbraco (all versions, incl. 18) pins ImageSharp to 3.1.x, so we can't move to 4.x. Any chance of a 3.1.13 release?

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions