Re: [Development] Memory leak in libQt5Core.so.5.15.7
Den tis 31 okt. 2023 kl 09:49 skrev Khande, Chandrakant Gulab (DBAN) : > > Hi Team, > > > > 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 > > ==1819== 312 bytes in 3 blocks are definitely lost in loss record 13,372 of > 14,268 > ==1819== at 0x4C388C3: operator new(unsigned long) (vg_replace_malloc.c:422) > ==1819== by 0x144555E7: QEventLoop::QEventLoop(QObject*) (in > /opt/Qt/lib/libQt5Core.so.5.15.7) > ==1819== by 0x14283480: QThread::exec() (in /opt/Qt/lib/libQt5Core.so.5.15.7) > ==1819== by 0x142846A2: ??? (in /opt/Qt/lib/libQt5Core.so.5.15.7) > ==1819== by 0x14BB81C9: start_thread (in /usr/lib64/libpthread-2.28.so) > ==1819== by 0x15738E72: clone (in /usr/lib64/libc-2.28.so) > > === > ==1766== 107 (40 direct, 67 indirect) bytes in 1 blocks are definitely lost > in loss record 11,877 of 14,215 > ==1766== at 0x4C39B6F: operator new[](unsigned long) (vg_replace_malloc.c:640) > ==1766== by 0x143DEB71: ??? (in /opt/Qt/lib/libQt5Core.so.5.15.7) > ==1766== by 0x143DA27C: ??? (in /opt/Qt/lib/libQt5Core.so.5.15.7) > ==1766== by 0x143DA403: QProcess::start(QString const&, QStringList const&, > QFlagsQIODevice::OpenModeFlag) (in /opt/Qt/lib/libQt5Core.so.5.15.7) > ==1766== by 0x143DA5D5: QProcess::start(QString const&, > QFlagsQIODevice::OpenModeFlag) (in /opt/Qt/lib/libQt5Core.so.5.15.7) > > > > Thanks, > > Chandrakant > > PROPRIETARY: This e-mail contains proprietary information some or all of > which may be legally privileged. It is intended for the recipient only. If an > addressing or transmission error has misdirected this e-mail, please notify > the author by replying to this e-mail. If you are not the intended recipient > you must not use, disclose, distribute, copy, print, or rely on this e-mail. I think this footer is incompatible with a publicly archived list like development@qt-project.org, so please omit it from future posts. > -- > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Memory leak in libQt5Core.so.5.15.7
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 smime.p7s Description: S/MIME cryptographic signature -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Memory leak in libQt5Core.so.5.15.7
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].) [0] https://bugreports.qt.io/ [1] https://rockylinux.org/ Eddy. -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Memory leak in libQt5Core.so.5.15.7
Hi Team, 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 ==1819== 312 bytes in 3 blocks are definitely lost in loss record 13,372 of 14,268 ==1819== at 0x4C388C3: operator new(unsigned long) (vg_replace_malloc.c:422) ==1819== by 0x144555E7: QEventLoop::QEventLoop(QObject*) (in /opt/Qt/lib/libQt5Core.so.5.15.7) ==1819== by 0x14283480: QThread::exec() (in /opt/Qt/lib/libQt5Core.so.5.15.7) ==1819== by 0x142846A2: ??? (in /opt/Qt/lib/libQt5Core.so.5.15.7) ==1819== by 0x14BB81C9: start_thread (in /usr/lib64/libpthread-2.28.so) ==1819== by 0x15738E72: clone (in /usr/lib64/libc-2.28.so) === ==1766== 107 (40 direct, 67 indirect) bytes in 1 blocks are definitely lost in loss record 11,877 of 14,215 ==1766== at 0x4C39B6F: operator new[](unsigned long) (vg_replace_malloc.c:640) ==1766== by 0x143DEB71: ??? (in /opt/Qt/lib/libQt5Core.so.5.15.7) ==1766== by 0x143DA27C: ??? (in /opt/Qt/lib/libQt5Core.so.5.15.7) ==1766== by 0x143DA403: QProcess::start(QString const&, QStringList const&, QFlagsQIODevice::OpenModeFlag) (in /opt/Qt/lib/libQt5Core.so.5.15.7) ==1766== by 0x143DA5D5: QProcess::start(QString const&, QFlagsQIODevice::OpenModeFlag) (in /opt/Qt/lib/libQt5Core.so.5.15.7) Thanks, Chandrakant PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
