Important: Please read the Qt Code of Conduct -

Animated FastBlur causes Qt Quick application to crash on exit

  • Hello.

    I have a problem with animated ShaderEffect, FastBlur. When application exits after playing animation it crashes with following statement: "Error - RtlWerpReportException failed with status code :-1073741823. Will try to launch the process directly".
    If I change ending radius value to 0. it will not crash on exit.
    Not sure if it's a bug or I made some mistakes that lead up to that.

    Application is the default Qt Quick 2.2 application (no changes) with following QML file:

    @import QtQuick 2.2
    import QtQuick.Window 2.1
    import QtGraphicalEffects 1.0

    Window {
    visible: true
    width: 360
    height: 360

    MouseArea {
        anchors.fill: parent
        onClicked: {
            if ( mouse.button == Qt.LeftButton ){
    SequentialAnimation {
        id: animations;
        NumberAnimation {
            target: coverBlur;
            property: "radius";
            from: 0.0;
            to: 64.0
            duration: 2000;
            easing.type: Easing.InOutQuad
        NumberAnimation {
            duration: 3000;
        NumberAnimation {
            target: coverBlur;
            property: "radius";
            from: 64.0;
            to: 0.0
            duration: 2000;
            easing.type: Easing.InOutQuad
    Rectangle {
        id: albumRect;
        width: parent.width;
        height: parent.height;
        color: "transparent";
            id: coverBlur;
            source: coverImg;
            anchors.fill: coverImg;
            radius: 64;
        Image {
            id: coverImg;
            smooth: true;
            anchors.rightMargin: 10;
            anchors.leftMargin: 10;
            anchors.bottomMargin: 10;
            anchors.topMargin: 10;
            anchors.fill: parent;
            source: "qrc:///cover.png";
            opacity: 1.0;
            fillMode: Image.PreserveAspectFit;
            visible: false;


  • Hi,

    It looks like a Bug, I tested your code and have the same issue..

    I have to look into it more deeply...

    I also found a related issue

  • So it was a bug after all. Thanks for reporting. Hope it will be resolved in Qt 5.3.

  • Issue seems to be solved in Qt5.3

Log in to reply