This seems to have been caused by a valid issue that was recently fixed for 5.3.1 (or 5.2.1 if that is imminent):
See https://bugreports.qt-project.org/browse/QTBUG-39393
↧