Resize in parallel throws AccessViolationException or gives artifacts

I’m getting some problems when I try to resize copies of an image multiple times in parallel. I’ve tried making a console application as simple as possible that demonstrates my issue:

class Program
{
    static void Main()
    {
        var originalFilepath = "C:\\original.png";
        var outputPath = "C:\\resized";
        Func<int, string> outputFilepath = i => $"{outputPath}\\{i}.png";
        var n = 1000;
        var width = 100;
        var height = 100;

        System.IO.Directory.CreateDirectory(outputPath);
        using (var originalImage = new MagickImage(originalFilepath))
        {
            var tasks = new List<Task>();
            for (int i=0;i<n;i++)
            {
                tasks.Add(ResizeAsync(originalImage, width, height, outputFilepath(i)));
            }

            Task.WhenAll(tasks).Wait();
        }
    }

    static async Task ResizeAsync(MagickImage originalImage, int width, int height, string outputFilepath)
    {
        await Task.Delay(1); 

        using (var resizeImage = new MagickImage(originalImage))
        {
            resizeImage.Resize(width, height);
            resizeImage.Write(outputFilepath);
        }
    }
}

If I run the above code using this image as original image: I will either get an AccessViolationException or get a number of resized images with artifacts such as:

I’m using Visual Studio 2015 and Magick.NET-Q8-AnyCPU 7.0.7.300

[ExplicitlyImplicit]

Using build 7.0.7.700 still yields the same kind of artifacts (I tried the console application above).

[dlemstra]

@ExplicitlyImplicit The new release was published yesterday, could you give it another try?