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
- Imposing conservative allocation limits by configuring a custom MemoryAllocator+ Imposing conservative allocation limits by configuring a custom MemoryAllocator with [`MemoryAllocationOptions.AllocationLimitMegabytes`](https://docs.sixlabors.com/api/ImageSharp/SixLabors.ImageSharp.Memory.MemoryAllocatorOptions.html#SixLabors_ImageSharp_Memory_MemoryAllocatorOptions_AllocationLimitMegabytes) set to a value lower value.
Link back the security docs from the property docs.
For both the MaximumPoolSizeMegabytes docs and AllocationLimitMegabytes can be more precise about defining the default value:
- null means platform default: 1GB on 32-bit processes, 4GB on 64-bit processes.+ The value is null by default, which means platform defaults will be used: 1GB on 32-bit processes, 4GB on 64-bit processes.
The text was updated successfully, but these errors were encountered:
Noting down a couple of improvement ideas after re-reading some docs I made.
MaximumPoolSizeMegabytes
docs andAllocationLimitMegabytes
can be more precise about defining the default value:The text was updated successfully, but these errors were encountered: