Hi, > delete ( ( QWidget * ) p->ph ); > delete p->ph; // this triggers multiple freeing > > So the test scenario I presented is wrong altogether. > only > delete ( ( QWidget * ) p->ph ); > is enough and operator in our stub is called. > > Good news is that hbXBP/demoxbp.exe stays almost > on the same level of memory usage, the phenomena hogging > me all the time. > > The bad news is, for some delete calls our operator is never > reached, especially after application exit, and fm log reports > unreleased memory block.
If you can precisely locate such an occasion, you can try to look up the internals in QT source code. This way you can track down what exactly gets executed. > Still under test scenario, will update if I could find anything useful. > > Viktor, is not it a good idea to put this stub in hbqt.lib itself ? No, we discarded the idea, as it might be possible that Harbour apps are used with other C++ projects (even private ones), where such HBQT specific solution wouldn't solve the problem. Also, making this trick local to HBQT would mean that it cannot be mixed with any other C++ project which does the same redirection in local code. So we concluded it should be in hbmk2. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
