QtQuick setSource leaks in certain cases

Our app loads different QMLs at different times in it's life-cycle instead of loading all QMLs pages and using the visible property. This is done to reduce memory footprint as we are targeting a memory restricted mobile device.

To switch pages we use QDeclarativeView->setSource

after a few (10-20) page changes the mobile device starts running out of memory using up to 1MB per page change.

I've recreated this behavior in this small example app on Windows 7 (not just on mobile platform). The leak is much small but still there.

Keep an eye on memory use of the app and start clicking on the QML panel (it will say dialog 1 and dialog 2 alternatively) You'll notice that the memory use keeps going up.

Note that using the mouse to trigger the page change is important. If you enable the timer inside the app to do the page changes no memory leak occurs!