Conversation
For me it's a mem leak in qt no ? |
|
That's not necessarily a leak in Qt. While this means that the memory was allocated by Qt internally, the question is more why it wasn't deleted. We've encountered similar issues before, where certain types were not quite compatible with the way CXX moves data around. I think that was with QTimeZone, but I unfortunately can't find our discussion on that. |
|
|
So it seems there are indeed more constructor (9) than destructor (6) calls. That's likely caused by CXX "forgetting" an instance, which we've encountered before. |
No description provided.