Hi István
Bisz István wrote: > > The demoqt tests with debug_new shows a lot of leaked objects , see > attached debug_new.txt. As I see now, the objects allocated by the new > operator are not released by a corresponding delete operator. > I am struggling with this aspect since 20 days and could not reached to any consclusion why Qt is not releasing the objects. To illustrate, just navigate in <Brw> tab in demoxbp and also keep an eye over task manager. You will be surprized to observe that memory keeps on growing all the time. Not only here, just move the mouse in/out of the demoxbp window, the same behavior will follow. And the worse is, if you play like this for a couple of hours, netxt time, demoxbp.exe will fail to load. You will need to reboot your computer. I was wondering why this happens. I rewrote and subclassed QMainWindow() and implemented it for XbpDialog() class to have finer control over events and their execution. However I could not avoid this behavior. And today you have confirmed that Qt itself is buggy on this front. Even I downloaded Qt 2009.03 and checked all above against it but the result is the same. Along with above issue, I have one more issue with Qt in respect to its paint engine which fails on MT scenario. I will post the modified code and will show what is needed to control it and what heavy penalty we have to pay. And thanks for stopping my frustration over the subject. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/demoqt-tests-with-debug_new---Leaked-objects-tp25434990p25440044.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
