Applications built with QT 5.0.1 leak ObjC objects because apparently no attempt is made to create an NSAutoreleasePool. I noticed this in my own build, but the ‘official’ clang64 build available for download has the same flaw, so it’s not an issue with my build procedure.
This is a memory leak but also a cause of severe logfile pollution.
I found some isolated posts/bug reports related to NSAutoreleasePools, but nothing more generalised.
Is this a known issue that’s already being addressed? If not, where would one do the NSAutoreleasePool creation and drain – in the QApplication constructor and destructor?
↧