UnmanagedImage should call AddMemoryPressure and RemoveMemoryPressure

[GoogleCodeExporter]

UnmanagedImage allocates unmanaged memory in several situations.

An UnmanagedImage that is never explicitly disposed of, will be garbage 
collected and have its finalizer called, thus freeing the unmanaged memory.

In such a scenario, it is recommended to call System.GC.AddMemoryPressure and 
System.GC.RemoveMemoryPressure to inform the garbage collector of the amount of 
unmanaged memory allocated, so that it can be taken into account when 
scheduling garbage collection.

I have attached a patch where I have made that change.

http://msdn.microsoft.com/en-us/library/system.gc.addmemorypressure.aspx
http://msdn.microsoft.com/en-us/library/system.gc.removememorypressure.aspx

Original issue reported on code.google.com by ncruces on 20 Mar 2013 at 1:35

Attachments:

• UnmanagedImage.cs.patch

[GoogleCodeExporter]

Original comment by andrew.k...@gmail.com on 20 Mar 2013 at 1:39

• Changed state: Accepted
• Added labels: Project-Imaging

[GoogleCodeExporter]

Added usage System.GC.RemoveMemoryPressurу()/AddMemoryPressure() to 
UnmanagedImage allocate/deallocation code.

Fixed in revision 1712.

Original comment by andrew.k...@gmail.com on 26 Jun 2013 at 9:23

[GoogleCodeExporter]

Original comment by andrew.k...@gmail.com on 26 Jun 2013 at 9:39

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by andrew.k...@gmail.com on 16 Jul 2013 at 9:54

• Changed state: Released