On Tuesday, 31 October 2023 02:35:43 PDT Edward Welbourne via Development 
wrote:
> Khande, Chandrakant Gulab (31 October 2023 09:48) wrote:
> > Found the memory leak in libQt5Core.so.5.15.7
> > Following is the valgrind stack, can Qt help to resolve this, any fix
> > version available for Rocky 8
> Please file a ticket in the bug tracker [0] - you may need to create an
> account to do so.  Attach the valgrind log and provide a test program
> that reproduces the issue, or at least give some clue to how to
> reproduce it.  (I see Rocky is yet another Linux [1].)

Do not file without a reproducer, because the only new in QEventLoop's 
constructor is the QEventLoopPrivate, so that issue makes it look like the 
whole QEventLoop got leaked, which can't happen because it is a stack 
variable.

The most likely scenario is that the application exited without waiting for 
all its threads to exit.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to