Possible memory leak of gradient animation

[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

[petero3]

@SeeLook this should be fixed now. I've retested my app with 6.10.2 and gputop now shows stable usage.
https://qt-project.atlassian.net/browse/QTBUG-136553

[SeeLook]

@petero3
Thanks for the update.
Because we have to stick to older Qt version I found workaround to use QQuickPaintedItem.
Visually it gives me the same effect and CPU impact (if any) is bearable.
... only hands were dirty :-)