Hi, On 08/06/2022 18:40, Thiago Macieira wrote:
On Wednesday, 8 June 2022 07:17:29 PDT Fabian Kosmale wrote:- There are concerns that mixing Qt versions might lead to an unbounded memory leak with the current implementation. I don't think that's actually the case (but if it is, then we need a different enough approach that this most likely has to be deferred to Qt 6.5 at least).
To be clear for everyone: this can happen (depending on where we introduce the new API) if some code is using QStringConverter with codec names that it currently doesn't support. This is likely to be very limited, because that code is currently not working (it always produces an invalid encoder/decoder). That probably means it's blind porting from QTextCodec which did support more codecs. The fix is to simply recompile.
Could you please elaborate a bit? What does "mixing Qt versions" mean in the above?
Thanks, -- Giuseppe D'Angelo | [email protected] | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
