I have found this blog post: https://dragotin.wordpress.com/2014/08/14/monitor-the-qobject-tree-of-a-qt-app/
I will try using these callbacks to monitor the QObject tree. They are absolutely undocumented (searching for the function name leads to the blog page as first result...), are they maintained/functional? Thanks! 2015-10-30 18:51 GMT+01:00 william.croc...@analog.com < william.croc...@analog.com>: > > >> Also, use techniques like QScopedPointer to simplify memory >> management. >> >> >> All this was done, especially in the QThread / QSocket part. But the app >> is >> complex and something may have been left out. >> >> > I had a similar problem. > You need to look for places where "things" could accumulate. > Check your QLists and QMaps in addition to the QObject > parent/child model. I assume you know the top level QObjects. > Recursively visit all children and dump the tree, with indentation > and inspect. > > Purify also has an option to show you all memory in use. > I assume that Valgrind has something similar. > > Bill > > > >> >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest >> > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
