From 305c0e53e43cfb76456c1daf3ef756b9761db07c Mon Sep 17 00:00:00 2001 From: Sean Killeen Date: Tue, 18 Oct 2022 21:45:12 -0400 Subject: [PATCH] fix: "discontiguous" --- articles/imagesharp/memorymanagement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/imagesharp/memorymanagement.md b/articles/imagesharp/memorymanagement.md index 7350478b..3526dbb3 100644 --- a/articles/imagesharp/memorymanagement.md +++ b/articles/imagesharp/memorymanagement.md @@ -1,6 +1,6 @@ # Memory Management -Starting with ImageSharp 2.0, the library uses large (~4MB) discontigous chunks of unmanaged memory to represent multi-megapixel images. Internally, these buffers are heavily pooled to reduce OS allocation overhead. Unlike in ImageSharp 1.0, the pools are automatically trimmed after a certain amount of allocation inactivity, releasing the buffers to the OS, making the library more suitable for applications that do imaging operations in a periodic manner. +Starting with ImageSharp 2.0, the library uses large (~4MB) discontiguous chunks of unmanaged memory to represent multi-megapixel images. Internally, these buffers are heavily pooled to reduce OS allocation overhead. Unlike in ImageSharp 1.0, the pools are automatically trimmed after a certain amount of allocation inactivity, releasing the buffers to the OS, making the library more suitable for applications that do imaging operations in a periodic manner. The buffer allocation and pooling behavior is implemented by @"SixLabors.ImageSharp.Memory.MemoryAllocator" which is being used through @"SixLabors.ImageSharp.Configuration"'s @"SixLabors.ImageSharp.Configuration.MemoryAllocator" property within the library, therefore it's configurable and replaceable by the user.