Hello Przemek, All I would like to have an analysis how Harbour implements garbage collection in GUI mode, I mean, where there is no inkey() or similar call ?
With last modifications in HBQT, changing the way destructors are called, all objects are being deleted properly. This I verified by accessing the deleted object again which GPFs. But still memory keeps on growing. What I suspect is, probably, that this could be related to GC in Harbour. All objects coming to PRG via "new" opeartor are returned as a pointer : hb_retptr( new QSomeObject() ) which are supposed to be covered by GC. But I am wondering at what point of application loop, Harbour is performing garbage collection. Any point leading to memory issue in HBQT will be of great help to push Harbour to next levels. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/HBQT---HBXBP-%3A-Garbage-Collection-tp25813841p25813841.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
