Congratulations to our 2022 Qt Champions!

Qt 5.3.0: process crash complaining about free() in QQmlImageProviderBase when closing QQuickView

  • Hello, I am working on a project recently migrated to Qt 5.3.0 (previously it was running on Qt 5.2.1).

    My project is based on a QQuickView object being filled with some QML files, depending on some command I receive from a communication protocol...

    Since I was on Qt 5.2.1 the system worked fine and was rock solid: never a problem. Now with Qt 5.3.0 if I close the QQuickView window the process crashes with the following output:

    bq. * glibc detected * /home/morix/devel/aesys/VLED/build/bin/VLED: free(): invalid pointer: 0x091ec694 *
    ======= Backtrace: =========

    (VLED is the name of my project in the output here above).

    It seems that some free() call in QQmlImageProviderBase is working on a unvalid pointer...

    Please consider that in my project I make use of a QQmlImageProviderBase-derived class to provide some "live" pixmaps to QML... but I don't think the problem is there: the code is very simple (simply returns some pixmaps previously inserted in a local collection) and furthermore with Qt 5.2.1 it works fine...

    I am working on Ubuntu Linux 12.04 LTS... but the problem is the same if I cross-compile the application for BeagleBone Black / TI AM335x... so it seems not to be an "environment-related" problem but rather a Qt problem...

    Does somebody else is experiencing such a problem with Qt 5.3.0? Any workaround?

    I created a very simply project for reproducing the issue: it can be found "here":

    Please try it on your own and let me know if you have the same issue and if you find a valid workaround...

  • Lifetime Qt Champion


    Since you have a minimal project, you should take a look at the "bug report system": to see if it's something known. If not please consider opening a new report providing your sample application.

  • Ok SGaist: I followed your suggestion: the issue has been filed to the bug report system as "QTBUG-39621":

    I am going to update this discussion thread as soon as I have some news about it.

Log in to reply