-
Bug
-
Resolution: Done
-
Not Evaluated
-
5.3.0 RC1
-
None
-
I7ab0b5f47ecec6cb3cdded0dd219d6acc1bc4148
Since QtQuick2, the AnimatedImage component is less efficient than it was with QtQuick1. In fact, it uses more CPU and memory to work properly.
To point out the issue, I made two similar applications, the first one using QtQuick1.1 and the second one using QtQuick 2.2. I compiled both applications with Qt 5.3.0 RC1 for Windows (MinGW) and I got the following results with a Intel Core i7-3610QM 2.3 GHz processor and a NVidia GeForce 670M GTX graphic card :
- QtQuick1.1 : 0% of CPU, 22Mo of RAM
- QtQuick2.2 : 5% of all my threads (if you combine, it represents 40% of one thread), 54Mo of RAM.
I think the RAM usage is not really important (it just requires AnimatedImage to use a cache system), but the CPU usage may be really embarrassing on mobile platform. It's probably related to the scene graph.
Please feel free to ask more information if you need.
- relates to
-
QTBUG-64272 AnimatedImage uses a lot of memory when caching is enabled
-
- Open
-
-
QTBUG-70730 When an AnimatedImage is continually running then it can end up crashing due to lack of memory
-
- Closed
-
-
QTBUG-31872 AnimatedImage crashes with GIF
-
- Closed
-
-
QTBUG-39217 Animated image loaded from network produces warnings
-
- Closed
-
- resulted in
-
QTBUG-64272 AnimatedImage uses a lot of memory when caching is enabled
-
- Open
-
For Gerrit Dashboard: QTBUG-38921 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
86467,3 | Optimize the way AnimatedImage display its content | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |