前階段在調研mobile上的內存釋放問題,根據大家的建議嘗試了一些,但是沒有什么效果。
于是跑到MSDN上去問相關的問題,得到了一些解答。
As far as I know, I don't think there is other way to meet your requirement. Since each mobile application has 32M memory limitation, we have to do the performance manually, like deleting object which is not used and allocating Large Memory Blocks in Large memory Area.
For more information:
Windows CE .NET Advanced Memory Management
How the Windows Mobile 5.0 Shell Handles Low Memory Situations
我看了一部分,在How the Windows Mobile 5.0 Shell Handles Low Memory Situations中提到,

Hibernate
This is the amount of memory the shell tries to keep free at all times. If the amount of free memory falls below this value then the low memory check routine will try to free up memory. It will do this by first sending WM_HIBERNATE to all valid applications. When an application receives this message it should try to free as many resources as possible. When the low memory check routine runs again and the amount of free memory is still below the hibernate level then the shell will try to close the least recently used (LRU) application by sending a WM_CLOSE message. If the low memory check routine runs yet again and the amount of free memory is still below the hibernate level then the shell will call TerminateProcess on the LRU application that it last sent the WM_CLOSE message to.
我對這段話的理解是:當空閑內存小于Hibernate時,系統便會嘗試釋放內存。首先他會向所有有效的程序發送WM_HIBERNATE。應用程序收到該消息后,會盡量釋放資源來釋放內存。如果還低于這個值的話,將發送WM_CLOSE消息給最近很少使用的程序。如果還低于該值的,就強行關閉該程序了。
這個方法似乎有效,但是用戶再起來程序的話,還是一樣的效果,并不是達到了什么釋放內存的效果。如何記錄最近很少使用的程序,這個是不是有什么方法獲得呢?
就可以像系統提示的那樣,內存不足,請釋放一些內存。手工做一些比較好。
也看了一些相近的程序的做法,似乎效果也沒有大家說的那么好。
在How the Windows Mobile 5.0 Shell Handles Low Memory Situations的最后,這樣寫的
What can my Application do?
The best thing your application can do when faced with a low memory situation is to play nicely with the rest of the device.
1、If your application receives a WM_HIBERNATE message free up any resources not absolutely required.
2、If you are planning on allocating a large amount of memory (or if a large allocation fails) you should call SHCloseApps, which will invoke the shell low memory check routine and will try to ensure that enough free memory exists. See below for an example:
#define MIN_MEMORY_TO_RUN 2*1024*1024

MEMORYSTATUS mst;

mst.dwLength = sizeof(MEMORYSTATUS);

GlobalMemoryStatus(&mst);

If (mst.dwAvailPhys < MIN_MEMORY_TO_RUN)



{

// Try to free memory by asking Shell to shutdown apps

if (!SHCloseApps(MIN_MEMORY_TO_RUN))


{

// Handle the case where memory could not be freed

…


專門查了一下
SHCloseApps的用法
原型:BOOL SHCloseApps( DWORD dwMemSought);
功能:This function tries to free up memory for an application. If necessary, the shell closes down other applications by sending
dwMemSought);
功能:This function tries to free up memory for an application. If necessary, the shell closes down other applications by sending
WM_CLOSE messages.
參數:
dwMemSought Specifies, in bytes, the amount of memory to be freed.
通過了解
dwMemSought Specifies, in bytes, the amount of memory to be freed.
通過了解
SHCloseApps,我們就明白了上面那段代碼什么意思了。
看來,內存釋放并不是真正意義上的內存整理,看來我有的地方誤解了!
posted on 2009-03-05 13:56
Sandy 閱讀(1283)
評論(2) 編輯 收藏 引用 所屬分類:
windows學習