This is an old revision of the document!


01. [30p] RAM Monitoring

:!: Using Windows Performance Recorder, run a program that allocates 1MB of memory every 100 milliseconds for a while and then stops. After the program stops, save the capture, open it in Windows Performance Analyzer and analyze the Virtual Memory Snapshots graph. What conclusion can you draw by looking at the memory usage of the process that is running our program?

:!: Using VMMap, inspect the memory spikes generated by running the same program.

:!: Finally, after installing Visual Leak Detector and including the vld.h file to the program, inspect where the allocation took place. Do you observe any deallocations?

When writing the code, the following functions need to be overwritten: malloc, free, new, and delete. This allows each memory allocation and deallocation to be tracked. All the detected leakages (having an allocation that is not followed by a deallocation) will be saved in a log file that can be viewed after the program stops running.

ep/labs/09/contents/tasks/ex1.1638625621.txt.gz · Last modified: 2021/12/04 15:47 by andrei.mirciu
CC Attribution-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0