Memory usage

Sunil P V

Hi All, This query is regarding memory issue on WinXP (SP2). I have a simple application developed on MSVS2005 IDE. I am observing a peculiar behaviour of this application's memory usage when run on XP(SP2) machine: Internally i make use of the COM interface to access the database - MSADO. 1. WinXP(SP2 with WLAN API patch) - Memory usage around 9Mb 2. WinXP(Microsoft IDE 2005 with SP2 with WLAN API patch) - Memory usage around 26Mb Do anyone have any idea behid this dire memory consumption when the application is run on XP with Visual Studio being installed. Thanks in advance for your time and support...

Sunil

Stuart Dootson

Some questions -

Is this a debug or release build
Are you running the application under VS2005 when you get the 26MB memory usage

Maybe you could use Dependency Walker[^] to see what DLLs are being loaded into the executable, maybe some of them are Visual Studio related?

Lost User

Hi Sunil, Microsoft Windows will map many extra DLL's into your process space which do not appear in a PE image dependency walker. These extra libraries which are mapped into your process can be completely different on each users machine. Some examples of extra dynamic link libraries which could be mapped into your process: 1.) AppInit_DLLs[^] 2.) Window Hooks[^] 3.) Application Compatibility Layer[^] (Much of the AppCompat/Shim Engine is NDA undocumented) 4.) Device Drivers may map extra DLL's into a process. If you want to visually inspect which libraries are loaded in each situation then I would recommend downloading Process Explorer by Mark Russinovich[^]. You can export your process information to a text file and differentiate them. Best Wishes, -David Delaune