You are right.
Since Update 6, the tool supports to report "Memory Growth" problem, it occurs when a block of memory is allocated but not deallocated within a specific time segment during application execution.
Here is my simple example code for testing:
Create an Inspector XE projecton GUI to run"Locate MemoryProblem" with program, click "Start" button, afterawhile click "Set Transaction Start"...run program awhile again...click "Set Transaction End". Finally click "Stop" button to terminate application, to get report below.
What I saw is "Memory Growth" problem given, and problematical source allocation was pointed out. However
Object Size is empty, so we can detect it butcannot find exactsize for this memory growth problem.
I will verify this problem with engineering team, and update this soon.
How do you define that value? Howcould I know it in advance?
1. Thereare dynamicalgorithms and it is impossible to predict how much memory will be needed for
processing, when it will be requested and when it will be released.
2. Some applications are pre-allocating huge amounts of memory in advance,then usememory and before
exit deallocate.In that scenario there are no Memory Growth problem and there are no Memory Leaks.
So, the Memory Growth concept looks confusing.
3. Some applications are pre-allocating huge amounts of memory in advance,then usememory and before
exit "drop" itand it iscalled as Enforced Memory Leaks. It makes exit for the applicationfaster.
PS: I'll provide latera screenshot of howEnforced Memory Leaks works.