Memory usage has been discussed before. I think for instance this thread [qt-project.org] might be useful.
I think it is often misleading to look at the current memory usage this way as the garbage collector won’t kick in unless it has to. It is clearly a bug if the memory use continues to grow unbounded but I suspect it stabilises at some point.
If you are looking for possible ways to reduce the initial memory footprint I suspect setting a custom TableViewStyle (or just a custom row delegate) might help a bit as quite a bit of the memory is possibly related to having to resize and re-request pixmaps from the native theme engine during a resize.
Note that already in 5.3 we have modified the TableView to mostly re-cycle constructed delegates rather than allocating new ones (which should still get garbage collected after a while) and that might possibly make a significant impact on reducing the memory allocations as well as total memory use. Could be interesting to re-run your experiment on the 5.3 beta.
↧








