There was a recent issue (see my last question) which inspired me to ignore memory management in my Delphi.
Application. After my first search, I have two questions.
I started playing with FastMMUs Tracker, and noticed the following. When I open the file used by the app (which creates a form etc ...), there is a significant discrepancy between variation in available virtual memory for the app and the difference between "FastMM4 allocated" memory. / P>
First of all, I'm a little confused with the terminology: Why are some FastMM allocated memory and some "system-allocated" (and reserved) storage? Since FastMM is a memory manager, why is there a system to allocate some memory?
In addition to this, how can I get more information about the object that has been allocated to that memory? The VM chart is useful only to show the amount of "system allocated", "system reserved" or "fastmm allocated" memory, but there is no link to the actual object that needs the storage. Is it possible to get reports for example, mid-execution, what does the FastMM generate on application? FastMM clearly stores that information somewhere
As a bonus to me, if people have a good reference on the topic (book, website) If recommended, it would be greatly appreciated. There is a lot of information on the net, but it is usually very specific and oriented to the experts.
Thank you!
PS: This is not about finding a leak, there is no problem, just trying to understand memory management better and trying to become a pre-tool for the future, because our The application uses more memory.
Some of your questions are easy, okay, one of them too!
Why are some FastMM allocated memory and some "system-allocated" (and reserved) memory? Since fastmem is memory manager, why is there a system to allocate some memory?
The code written in Delphi is only part of the process that runs in your process. You use 3rd party libraries as DLL, especially at the Windows API any time you create a delphi form, for example, there are many window objects behind it that consume memory, not all of this memory is allocated by FastMM And I think your question is called "system-allocated."
However, if you want to go deeper, then it becomes a very complex subject very fast. If you want to go deep into the implementation of Windows Memory Management, then I think you need to consult a serious reference source. I recommend by Mark Rysovitch, David Solomon and Alex Eiosco.
Comments
Post a Comment