Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Valgrind not detecting memory leak after QObject connected
Forum Updated to NodeBB v4.3 + New Features

Valgrind not detecting memory leak after QObject connected

Scheduled Pinned Locked Moved Unsolved General and Desktop
2 Posts 2 Posters 264 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    random_user
    wrote on last edited by
    #1

    Hello, I'm new to using Valgrind and wanted to use it in a large project. Before that, I wrote a simple test to create a memory leak on purpose and see the output. But I failed to do so in a very specific case. When a QObject is created using new then connected via a signal/slot mechanism, Valgrind fails to detect it even if delete is not called !

    7  int main(int argc, char *argv[])
    8  {
    9    QCoreApplication app(argc, argv);
    10
    11    Test* t = new Test();
    12
    13   /* Memory leak detected by Valgrind */
    14    QTimer* timer_1 = new QTimer();
    15
    16    /* Memory leak NOT detected by Valgrind */
    17    QTimer* timer_2 = new QTimer();
    18    QObject::connect(timer_2, SIGNAL(timeout()), t, SLOT(timeoutSlot()));
    19
    20    /* Memory leak detected by Valgrind */
    21    QTimer* timer_3 = new QTimer();
    22    QObject::connect(timer_3, SIGNAL(timeout()), t, SLOT(timeoutSlot()));
    23    QObject::disconnect(timer_3, SIGNAL(timeout()), t, SLOT(timeoutSlot()));
    24
    25    return 0;
    26 }
    

    Test is a simple QObject subclass with one slot doing nothing.
    And here is what Valgrind output looks like:

    144 (32 direct, 112 indirect) bytes in 1 blocks are definitely lost in loss record 33 of 39 | Location main.cpp:14
    376 (32 direct, 344 indirect) bytes in 1 blocks are definitely lost in loss record 36 of 39 | Location main.cpp:21
    504 (16 direct, 488 indirect) bytes in 1 blocks are definitely lost in loss record 37 of 39 | Location main.cpp:11
    

    As you can see, memory leak on line 17 does not appear.

    If possibly some memory leak escapes valgrind output, how can I make sure this does not happen in a larger project with many new, connect, etc ?

    For the setup, I'm using QtCreator and the default Valgrind installation, no specific parameters were introduced.

    Thank you

    1 Reply Last reply
    0
    • Christian EhrlicherC Offline
      Christian EhrlicherC Offline
      Christian Ehrlicher
      Lifetime Qt Champion
      wrote on last edited by
      #2
      int main(int argc, char *argv[])
      {
        QCoreApplication app(argc, argv);
      
        /* Memory leak detected by Valgrind */
        QTimer* timer_1 = new QTimer();
      
        /* Memory leak NOT detected by Valgrind */
        QTimer* timer_2 = new QTimer();
      
        /* Memory leak detected by Valgrind */
        QTimer* timer_3 = new QTimer();
      
        return 0;
      }
      

      With this code valgrind properly shows 3 memleaks.

      Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
      Visit the Qt Academy at https://academy.qt.io/catalog

      1 Reply Last reply
      1

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved