Severe Memory Leak

... any idea CJ team ?

Some more information:

Report control has 2 features to optimize memory usage.
This is useful for big amount of records (more than 10 000).

Let me note that features described below has real effect in Release build only.
In Debug build, program which used these features may work even slower than without them.

1. Custom Heap.
Some Report Control classes, which represent data (records, record items and rows),
has overridden new/delete operators which use own Allocator object to allocate/deallocate
memory on object create.
The allocator has 2 modes:
  1. Standard (by default) - the default application heap is used, as for any other Objects.
  2. CustomHeap      - the separate custom heap is used by this allocator.
                      (See HeapCreate and other related Windows API functions)

Allocator manage custom heap internally.
When all objects deleted - allocator destroy heap (and create again for next allocations).
This "Really" free all memory after all data removed and avoid Heap fragmentation problem.

Also by default Allocator enable "Low-fragmentation Heap" (LFH) feature for custom heap.
This optimize heap work in WinXP and later. But it does not works under debugger.

2. Batch Allocation.
If we need to allocate many objects of the same type (size) it is more effective
to allocate memory not for each object separately, but for some amount of such objects at one time (by batch).

Batch Allocation implemented over Custom heap.
This means that it can alloc batches in the standard heap as far as in the custom heap.

When you call "new" for some batch allocable class,
Batch Allocation mechanism allocate block for 1024 objects in the heap,
return pointer for one object and add other 1023 to "Free List".
For feature allocations objects from this "Free List" will be returned instead of new allocation in the heap.
When free list will be empty - new batch block will be allocated and added to "Free List".

When such object deleted (operator delete called) - it is added to "Free List" too (and will be used again for future allocations).

This is increase allocation/deallocation speed and allow to avoid heap fragmentation.

Batch Allocation manage list of batch blocks and list of free objects in each block.
When all objects from some batch block is in free list - such block deleted automatically.
FreeExtraData() method allow to delete these batch blocks from memory (from heap).

This means that you have to call FreeExtraData after Remove All records and rows to really free memory.
But if you plan to add some data again you should not do this.
In this case you may call FreeExtraData after add new records and populate.

--
WBR,
Serge

I had a confirmation from already closed Issue: