Unix | Embedded Linux | QNX | Firmware | Consulting | Development
Excessive use of malloc()/free() and/or new/delete can cause severe performance problems in you application even if no memory leak is present. Malloc statistics ( see below ) can outline threads which are excessively allocating and deallocating, but where are the lines in code which cause the problem? Invader allows you to nail these as well, by seleting the thread, selecting the allocated size of the memory chunk and select "Memory usage" instead of "Memory leak". You will see the stack trace of the code which causes the problem in your application.
© C++ World KG