My guess for this is this:
* There is one thread in Qt doing asynchronous loading for file, http and custom-provider images
* The images on the dash are asynchronous
* The Qt thread doing asynchronous loading pauses processing requests if there's 8 http requests going on
* If the internet is slooooow it may happen that there is 8 http requests going on and thus the file local ones are stalled until one of the http ones finishes
My guess for this is this:
* There is one thread in Qt doing asynchronous loading for file, http and custom-provider images
* The images on the dash are asynchronous
* The Qt thread doing asynchronous loading pauses processing requests if there's 8 http requests going on
* If the internet is slooooow it may happen that there is 8 http requests going on and thus the file local ones are stalled until one of the http ones finishes
Qt 5.6 will have a fix for this (and so will be if we backport the QQuickAsyncImag eProvider patch as planned https:/ /codereview. qt-project. org/#/c/ 108540/ )
I can also provide small patches against Qt 5.3 and Qt 5.4 if we want to carry those.