Click to Rate and Give Feedback
MSDN
MSDN Library
.NET Development
.NET Framework 3.5
System Namespace
GC Class
GC Methods
 RemoveMemoryPressure Method
Collapse All/Expand All Collapse All
This page is specific to
Microsoft Visual Studio 2008/.NET Framework 3.5

Other versions are also available for the following:
.NET Framework Class Library
GC..::.RemoveMemoryPressure Method

Informs the runtime that unmanaged memory has been released and no longer needs to be taken into account when scheduling garbage collection.

Namespace:  System
Assembly:  mscorlib (in mscorlib.dll)
Visual Basic (Declaration)
<SecurityPermissionAttribute(SecurityAction.LinkDemand, UnmanagedCode := True)> _
Public Shared Sub RemoveMemoryPressure ( _
    bytesAllocated As Long _
)
Visual Basic (Usage)
Dim bytesAllocated As Long

GC.RemoveMemoryPressure(bytesAllocated)
C#
[SecurityPermissionAttribute(SecurityAction.LinkDemand, UnmanagedCode = true)]
public static void RemoveMemoryPressure(
    long bytesAllocated
)
Visual C++
[SecurityPermissionAttribute(SecurityAction::LinkDemand, UnmanagedCode = true)]
public:
static void RemoveMemoryPressure(
    long long bytesAllocated
)
JScript
public static function RemoveMemoryPressure(
    bytesAllocated : long
)

Parameters

bytesAllocated
Type: System..::.Int64
The amount of unmanaged memory that has been released.
ExceptionCondition
ArgumentOutOfRangeException

bytesAllocated is less than or equal to 0.

-or-

On a 32-bit computer, bytesAllocated is larger than Int32..::.MaxValue.

In determining when to schedule garbage collection, the runtime takes into account how much managed memory is allocated. If a small managed object allocates a large amount of unmanaged memory, the runtime takes into account only the managed memory, and thus underestimates the urgency of scheduling garbage collection. The AddMemoryPressure method informs the runtime of this additional pressure on system memory, and the RemoveMemoryPressure method informs the runtime that the additional pressure has been released.

In the simplest usage pattern, a managed object allocates unmanaged memory in the constructor and releases it in the Dispose or Finalize method. Call the AddMemoryPressure method after allocating the unmanaged memory, and call the RemoveMemoryPressure method after releasing it.

In more complicated scenarios, where the unmanaged memory allocation changes substantially during the lifetime of the managed object, you can call the AddMemoryPressure and RemoveMemoryPressure methods to communicate these incremental changes to the runtime.

Caution noteCaution:

You must ensure that you remove exactly the amount of pressure you add. Failing to do so can adversely affect the performance of the system in applications that run for long periods of time.

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

.NET Framework

Supported in: 3.5, 3.0, 2.0
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement | Site Feedback
Page view tracker