diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-50CA5439-29A1-426C-83BA-EC048FE86CDE.dita
--- a/Symbian3/SDK/Source/GUID-50CA5439-29A1-426C-83BA-EC048FE86CDE.dita Wed Mar 31 11:11:55 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-50CA5439-29A1-426C-83BA-EC048FE86CDE.dita Fri Jun 11 12:39:03 2010 +0100
@@ -1,52 +1,52 @@
-
-
-
-
-
-Allowing
-Large Memory AllocationThis section describes how an application can request for free
-memory from OOM Monitor for large amount of RAM allocation.
-
An application
-can allocate RAM without seeking the permission from the OOM Monitor if the
-amount of RAM is not over KOomMaxAllocationWithoutPermission limit.
-
If an application needs to allocate more RAM than allocated by KOomMaxAllocationWithoutPermission,
-it must request the OOM Monitor using the ROomMonitorSession::RequestFreeMemory() method.
An
-application can request for free RAM either synchronously or asynchronously.
-
-
-Create an OOM Monitor
-session
-ROomMonitorSession ioomMonitorSession;
-CleanUpClosePushL(ioomMonitorSession);
-User::LeaveIfError(ioomMonitorSession.Connect());
-
-
-Request for free
-memory can be done in two ways:
-
-
-
The OOM Monitor
-allows the client application to allocate memory, if the free RAM level is
-above the LOW_RAM_THRESHOLD value.
If the free RAM
-level is below the LOW_RAM_THRESHOLD value,
-the OOM Monitor releases RAM using ROomMonitorSession::RequestFreeMemory() method.
-This method returns the following values:
-
Requested amount of RAM is available then aStatus is
-set to KErrNone.
-
Requested amount of RAM is not available then aStatus is
-set to KErrNoMemory.
-
-
-OOM Monitor
-Concepts
-OOM Monitor
-Overview
-OOM Monitor
-Reference
+
+
+
+
+
+Allowing
+Large Memory AllocationThis section describes how an application can request for free
+memory from OOM Monitor for large amount of RAM allocation.
+
An application
+can allocate RAM without seeking the permission from the OOM Monitor if the
+amount of RAM is not over KOomMaxAllocationWithoutPermission limit.
+
If an application needs to allocate more RAM than allocated by KOomMaxAllocationWithoutPermission,
+it must request the OOM Monitor using the ROomMonitorSession::RequestFreeMemory() method.
An
+application can request for free RAM either synchronously or asynchronously.
+
+
+Create an OOM Monitor
+session
+ROomMonitorSession ioomMonitorSession;
+CleanUpClosePushL(ioomMonitorSession);
+User::LeaveIfError(ioomMonitorSession.Connect());
+
+
+Request for free
+memory can be done in two ways:
+
+
+
The OOM Monitor
+allows the client application to allocate memory, if the free RAM level is
+above the LOW_RAM_THRESHOLD value.
If the free RAM
+level is below the LOW_RAM_THRESHOLD value,
+the OOM Monitor releases RAM using ROomMonitorSession::RequestFreeMemory() method.
+This method returns the following values:
+
Requested amount of RAM is available then aStatus is
+set to KErrNone.
+
Requested amount of RAM is not available then aStatus is
+set to KErrNoMemory.
+
+
+OOM Monitor
+Concepts
+OOM Monitor
+Overview
+OOM Monitor
+Reference
\ No newline at end of file