Memory leak in libQt5Core.so.5.15.7
-
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) -
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)@chandrakant2023 said in Memory leak in libQt5Core.so.5.15.7:
can Qt help to resolve this
This is Qt user forum.
If you want to ask developers of Qt then you should go to their developers mailing list.
And keep in minf that Valgrind often reports false positives for Qt. -
@chandrakant2023 said in Memory leak in libQt5Core.so.5.15.7:
can Qt help to resolve this
This is Qt user forum.
If you want to ask developers of Qt then you should go to their developers mailing list.
And keep in minf that Valgrind often reports false positives for Qt.And if you really want to report this then you should install the Qt debug information first to get the line numbers.
-
@chandrakant2023 said in Memory leak in libQt5Core.so.5.15.7:
can Qt help to resolve this
This is Qt user forum.
If you want to ask developers of Qt then you should go to their developers mailing list.
And keep in minf that Valgrind often reports false positives for Qt. -
@jsulm Thank you for this inputs.
Can you help me point to correct channel or developer mailing list please ?
