On Tue, Feb 4, 2020 at 5:18 PM Mårten Nordheim <marten.nordh...@qt.io> wrote:
> It’s likely related to the new network connection monitor inside > QNetworkAccessManager, which uses COM. > > Although that by itself shouldn’t cause any issues and there’s other uses > of COM inside Qt as well. But perhaps you didn’t indirectly use it so you > didn’t get a conflict earlier. > > [...] > This sounds familiar. We ran into a similar issue with QFileDialog crashing due to the wrong COM threading model being active. I do not recall the details, but searching for "CLR Thread Attribute" (a linking parameter) may give you some useful information. Cheers, Rainer -- Software Engineer | Trimble Imaging Division Rotebühlstraße 81 | 70178 Stuttgart | Germany Office +49 711 22881 0 | Fax +49 711 22881 11 http://www.trimble.com/imaging/ | http://www.inpho.de/ Trimble Germany GmbH, Am Prime Parc 11, 65479 Raunheim Eingetragen beim Amtsgericht Darmstadt unter HRB 83893, Geschäftsführer: Rob Reeder, Jürgen Kesper
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
