DevHealth and DevHealthViewer
As many of you know, MemoRX should not be used for Windows Mobile 6.1 development, instead we recommend developers to use DevHealth & DevHealthViewer. The DevHealthViewer tool replaces MemoRX and displays much more information than what MemRX did. Typically you will run DevHealth to capture a snapshot of your virtual memory usage (the log file is called mem_X.txt), run the tests, and then run DevHealth again to capture the virtual memory snapshot after the test. By using DevHealthViewer, you can visually compare the two memory snapshots and see which process is leaking memory during your test. Though DevHealth & DevHealthViewer do not tell you which function or module leaks the memory, it will point the process you should focus on. From here, you can use other tools such as Application Verifier to shim the module and gather the callstack for memory leaks!
