Error "UNINITIALIZED READ" in Dr. Memory report



  • Hello.

    I'm using Dr. Memory tool to check my software for memory leaks and other errors.

    Unfortunately, I always get a zillion of errors of type "UNINITIALIZED READ" that refer to Qt code. And if the trace goes through "my" code, it looks unsuspicious.

    The callstack looks like this
    @Error #4: UNINITIALIZED READ: reading 0x001deff0-0x001deff4 4 byte(s) within 0x001deff0-0x001deff4
    system call NtUserGetWindowPlacement
    QtGuid4.dll!QWidgetPrivate::setGeometry_sys
    QtGuid4.dll!QWidget::move
    ...@

    ...or this:
    @Error #4: UNINITIALIZED READ: reading 0x001deff0-0x001deff4 4 byte(s) within 0x001deff0-0x001deff4
    system call NtUserGetWindowPlacement
    QtGuid4.dll!QWidgetPrivate::setGeometry_sys
    QtGuid4.dll!QWidget::resize
    ...@

    Furthermore, in all places where I use QLibrary, I get:
    @Error #16: LEAK 56 direct bytes 0x0397b750-0x0397b788 + 460 indirect bytes
    replace_operator_new
    QtCored4.dll!QLibraryPrivate::findOrCreate
    ...@

    Is this just Dr. Memory going crazy?

    Or is this something I really should be concerned about?

    Regards,
    Mulder


  • Lifetime Qt Champion

    Hi,

    I'd say that they are probably false positive however you should rather ask this on the interest mailing list to get a more definitive answer.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.