I am using VS2008 SP1 and Qt 4.6.2. My project is linked with VLD 2.0b.
In vld.ini, I specified "ForceIncludeModules = QtCored4.dll QtGuid4.dll QtXmld4.dll ..." so the Qt dlls are properly watched by VLD.
Unfortunately, VLD says there is a huge amount of leaks in Qt. I found out it is due to VLD being destroyed before Qt's global objects (most of them constructed using the Q_GLOBAL_STATIC helper macro).
Here are two screenshots of call stacks taken during process shutdown: one taken when the
VLD object is destroyed (happens first), and another taken when
Qt global data is destroyed (happens later). Only the main thread exists.
Any idea why VLD this is happening? Is there a way to have the vld object destroyed last? Is the module load order (as shown by the visual studio debugger in the output pane) likely to influence the object destruction order? If so, how to change the dll
Thanks for your time and keep up the great work,