I noticed that all of the leaks mentioned in the file is during SHUTDOWN, which I personally don't care for. What I am more concerned with is memory leak during runtime. Is there away to capture runtime memory leak in heap.trc?
oh I see...No that is your start of the problem, do you have any controls created dynamically? Are they Components and if yes do they have proper ownership? after that look for dynamically created non components in that file do you have a destroy event to free them? IF not why?
You are right about FormDestroy. All of the memory leak that is listed in heaptrc is at SHUTDOWN.
However, all it says is "at line 733 in epmain.pas." you go there and it is of course FormDestroy. This is too vague. In this case, it could be anything. If your program contains 100 files, it would be like finding a needle in a haystack.
I guess I need to look for something else. :)
i see...Yes, "top" simply type top in a terminal. https://www.lifewire.com/linux-top-command-2201163 and https://linux.die.net/man/1/top
but are there any linux program like process viewer for windows that I can run on Linux OS that will enable me to see my software running live and all the resources it is using?
All the leaks leakview with heap.trc has shown me so far are nothing but leaks that I can indefinitely IGNORE. Yes, I do see in some of my code where I do create a variable or an object that can be released after the software is done using them, but it is not necessary. They go away when you shutdown your program anyhow. The leaks I am really interested in are the ones that are created repeatedly and not released during run time.And with that you created a chicken and egg problem.
All the leaks leakview with heap.trc has shown me so far are nothing but leaks that I can indefinitely IGNORE.If you do that under my watch you are fired. A memory leak in a compiled language is something you must never, ever ignore.
I thought memory leak is when a program or a process keeps on hogging resources little at a time over long period of time. Eventually, that leading to system failure or program crash not when for instance...