- The first part is built into the Engine code itself. When active (see Quickstart guide at the bottom of this document), it records every allocation and every free to disk
- The second part is a standalone application which analyzes the data to produce readable information, pretty graphs and tree maps
Example of MemReplay tool after loading
MemReplay helps to detect hidden errors in handling memory which, in the worst case, causes the application to crash. It has the following main purposes:
- Finding expensive memory allocations which can lead to "Out of memory"
- Measuring per system/class memory usage
- Finding memory leaks
- Locating memory tramples
- Finding Double frees
In This Topic
- Getting Started with MemReplay — Quick overview of how to collect memory information from a running instance of CRYENGINE.
- Setup and Loading data with MemReplay Tool — How to setup MemReplay for first use.
- Online Recording in MemReplay — Instructions for connecting MemReplay to a running instance of CRYENGINE via a network socket.
- MemReplay Tool at First Sight — An overview of the interface and basic features of MemReplay.
- MemReplay Tool Advanced Knowledge — An overview of advanced MemReplay features such as inspecting the heap or tracing allocation history.
- MemReplay in Code — An explanation of how allocation tracking is undertaken in CRYENGINE code.