Possible memory leak of gradient animation

[SeeLook]

@mzimmers
When duration time is constant the memory usage is constant as well.

[SeeLook]

So far it seems not like a bug but intended caching.
I tried to remove/create this tree path every time the animation starts but no RAM is released:

property var tree: Qt.createComponent("TreeShape.qml").createObject(pathWin)

  NumberAnimation {
    id: goAnim
    running: true
    target: pathWin
    property: "grAnim"
    from: 0; to: 1
    duration: animDur
    onFinished: {
      animDur = 500 + Math.random() * 10000
      tree.destroy()
      tree = Qt.createComponent("TreeShape.qml").createObject(pathWin)
      backAnim.start()
    }
  }

So maybe it would be more proper to ask how to clean this cache?

[mzimmers]

@SeeLook from your description, this doesn't really seem like a true memory leak; it's more just a really memory-intensive application. I'm assuming that once it hits the 300 MB mark, it remains relatively steady?

[SeeLook]

@mzimmers
Unfortunately not.
The app is working on 1GB device and it crashes after 30 min of work exactly because of this kind of animation.
So I'm looking for solution.
If there is no simpler way, maybe I will try to implement that in C++ using QQuickPainedItem.

[jsulm]

@SeeLook Use a memory profiler (like Valgrind) to see what eats the memory.

[SeeLook]

@jsulm
Ok. Let's try. But please help me to interpret it:
memAtPeak.png

I can see that QQuickShapeGradientOpenGlCache takes 16 MB at peak but only 357 KiB at start.
Shall I share this massif tool dumped data?

[jsulm]

@SeeLook 16MB is not much, would be interesting to see it when a lot more RAM is used

[SeeLook]

@jsulm
Ok I will launch it again and share data.

[SeeLook]

@jsulm
After about 20 min.
massif_20min.png
.. and probably it would grow and grow

Here is full massif file

[jsulm]

@SeeLook Could be a bug in Qt. You can file a bug at https://bugreports.qt.io/secure/Dashboard.jspa

[JKSH]

The problem is that every unique value of grAnim causes a new texture to be generated and stored in the cache: https://bugreports.qt.io/browse/QTBUG-136553