Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-61754

Change image source cause memory leak

    XMLWordPrintable

Details

    • 768f606cd3cd37c235e85225127201a42d272946

    Description

      This not affects with 5.9.0 and 5.8.0. An example in attachment. 

      Here's main.qml from the attachment:

      main.qml
      import QtQuick 2.7
import QtQuick.Controls 2.1

ApplicationWindow {
    visible: true
    width: 800
    height: 600

    Timer {
        interval: 200
        repeat: true
        running: true
        onTriggered: {
            var tmp = fstImage.source
            fstImage.source = sndImage.source
            sndImage.source = tmp
        }
    }

    Row {
        Image {
            id: fstImage
            width: 400
            cache: false
            source: 'qrc:/images/arrow.png'
            fillMode: Image.PreserveAspectFit
        }

        Image {
            id: sndImage
            width: 400
            cache: false
            source: 'qrc:/images/back.png'
            fillMode: Image.PreserveAspectFit
        }
    }
}

      Attachments

        1. arrow.png
          19 kB
          Amin Cheloh
        2. back.png
          12 kB
          Amin Cheloh
        3. main.qml
          0.7 kB
          Amin Cheloh
        4. qtbug61754.tar.gz
          32 kB
          Mitch Curtis
        5. qtbug61754-2.tar.gz
          159 kB
          Joni Poikelin
        6. valgrind-log-5.9.0.text
          118 kB
          Amin Cheloh
        7. valgrind-log-5.9.1.text
          122 kB
          Amin Cheloh
        8. valgrind-log-5.9.1-fix-memory-leak.text
          93 kB
          Amin Cheloh

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62613 Memory Leak with Images

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62642 Texture memory not being freed after component destruction

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-63514 Memory leak in ListView

          • P0: Blocker - MUST be fixed ASAP. This includes issues that prevent/block further Qt development; Legal issues & Serious data loss issues.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62524 High memory usage when updating QtQuick Image

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62600 QQuickImageProvider Memory Leaks

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62117 endSync never called from renderloop - leads to extreme memory use

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Activity

            People

              poikelin Joni Poikelin
              amincheloh Amin Cheloh
              Votes:
              5 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: