[Development] Qt 5.2 Beta, possible memory leak(s)

Koehne Kai Kai.Koehne at digia.com
Thu Oct 31 12:29:28 CET 2013

> -----Original Message-----
> From: development-bounces+kai.koehne=digia.com at qt-project.org
> [mailto:development-bounces+kai.koehne=digia.com at qt-project.org] On
> Behalf Of Luka Vilar
> Sent: Thursday, October 31, 2013 12:22 PM
> To: Kleint Friedemann
> Cc: development at qt-project.org
> Subject: [Development] Qt 5.2 Beta, possible memory leak(s)
> Hi,
> i agree and for the ICU part. Calling u_cleanup will free resources owned by
> ICU libraries. Converters used by Qt are already properly released so this is
> not an Qt issue.
> From ICU Api help: The use of u_cleanup() just before an application
> terminates is optional, but it should be called only once for performance
> reasons. The primary benefit is to eliminate reports of memory or resource
> leaks originating in ICU code from the results generated by heap analysis
> tools.

I'm not completely opposed to calling u_cleanup(), but we've to keep in mind that ICU API might get called very late (e.g. even in destructors of static objects, when someone decides to add say a qDebug() there). What happens if I call ICU API after u_cleanup() is called? Will it just miss data, or crash? This would need to be thoroughly tested ...



More information about the Development mailing list