QT Memory Leaks

[tbscope]

Suggestion for improvement using VLD:

1. Make sure you include the VLD header as the absolute very first header of your complete program.
2. Make sure that if VLD is a library, it is loaded as the very first library of your complete program.

While I don't think Qt is free of memory leaks, I don't think it contains 2400+ leaks. That's madness.

[SixDegrees]

I'm fairly sure that Qt does a lot of it's own memory management, bypassing malloc and new. This is certainly true for QStrings, which do a lot of referencing to avoid unnecessary data copies. Unfortunately, this sort of optimization hoses most leak checkers; a lot of them simply match calls to malloc/free or new/delete and note when there's an imbalance.

Since the number of leaks appears to be constant, rather than increasing with program load, I'd guess this is the case. See if your program actually consumes an increasing amount of memory over time and with increasing program load. If not, these reports can probably be safely ignored. I don't know what sort of tools are available for this under Windows; the Task Manager is notorious for giving bogus memory usage reports.

Note, too, that you may have to build Qt in debug mode in order to get the most useful information out of these tools; in release mode, they'll tend to be accurate, but not precise.

[hitesh_]

can any one plz tell me that how to use VLD whit Qt Creator 2.2.1
i have download "vld-10.zip"
in which i got following files
1) vld.h
2) vldapi.h
3) dbghelp.dll
4) vld.lib
5) vldmtdll.lib
6) vldmt.lib

plz help me that i acn use it with Qt Creator 2.2.1

[amleto]

I'm fairly sure that Qt does a lot of it's own memory management, bypassing malloc and new.

you can't allocate to the heap without malloc/new.

also, if you add -widgetcount (iirc) to command line options then Qt gives its own 'memory report' at the end.
http://doc.trolltech.com/4.6/qapplic...l#QApplication