Repro steps:

1. Use a QSortFilterProxyModel as a model to ListView
2. Set the ListView delegate to be a VectorImage and let the source be coming from the model as an ImageRole.
3. Then whenever the proxy model calls invalidate() the memory consumption increase for each time. 
4. VectorImage Component.onDestruction is called successfully and tests using Loader does not help.

I am not sure if all the steps above is necessary, but at least this provokes it. Also I am not sure if this is just a VectorImage fault or if there are mechanisms in ListView that causes this. Switching from VectorImage to Image remove almost all leak.

Attached is a minimal example on how to reproduce it, just add some .svg images. 

The memory is never freed in the lifetime of the application, calling gc() does not help either. 

Here you can see the memory increases each time "reshuffle" is called, from approx 3 to 5 sec in the graph, where I click reshuffle.