Windows: FileDialog and FontLoader don't work well together on some devices

When FileDialog is initialized after a FontLoader in QML, it seems to corrupt fonts or at least they are not being correctly painted. There are errors like this printed in the application output:

QWindowsFontEngineDirectWrite::addGlyphsToPath: GetGlyphRunOutline failed (The parameter is incorrect.)
QWindowsFontEngineDirectWrite::getSfntTableData: TryGetFontTable failed (The parameter is incorrect.)
QWindowsFontEngineDirectWrite::addGlyphsToPath: GetGlyphRunOutline failed (The parameter is incorrect.) 

Changing the order of FileDialog and FontLoader initialization reportedly works around the issue.

This seems to only occur on some devices. At least it was reproducible on Microsoft Surface Book 2.