Featured post
delphi - How much memory your program takes? (FastMM vs Borland MM) -
i have seen strange behavior in program. after creating large amounts of objects (500mb of ram) releasing them, program's memory footprint not return original size. still shows footprint of 160mb (private working set).
normal behavior?
borland's memory manager not behave this, if possible please confirm (or infirm) normal behavior fastmm: if have handy program in create rather complex mdi child (containing several controls/objects), can create in loop 250 instances of mdi child in memory (at same time) release them , check memory footprint. please make sure consume @ least 200-300mb or ram mdi childs.
especially still using delphi 7 can see difference temporary disabling fastmm.
thanks
if interested, if want proof not memory leak (i hope not mem leak in code - 1 of points of post: check if fault), here original discussions:
my program never releases memory back. why?
how convince memory manager release unused memory
iirc, delphi memory manager not return free'd memory os.
memory allocated in chunks of small, medium , large sizes, called blocks. these blocks kept while after contents have been disposed have them readyly available when allocation requested afterwards.
this limits amount of system calls required succesive allocation of multiple objects, , helps avoiding heap fragmentation.
- Get link
- X
- Other Apps
Comments
Post a Comment