Re: [Interest] Strange issue with Qt, OpenGL and remote desktop
Il 25/10/19 08:56, Rainer Wiesenfarth ha scritto: This is (still) QGL..., we have not yet switched to the QOpenGL... classes. Ok, so, to test if my random guess is remotely correct: get your QGLContext and connect to ctx->contextHandle()'s signal called aboutToBeDestroyed (i.e. check if that is getting called before problems appear). It's really a lick-finger-in-the-air kind of guess... HTH, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts smime.p7s Description: Firma crittografica S/MIME ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Strange issue with Qt, OpenGL and remote desktop
On Thu, Oct 24, 2019 at 10:23 PM Giuseppe D'Angelo via Interest < interest@qt-project.org> wrote: > Il 24/10/19 17:57, Rainer Wiesenfarth ha scritto: > > We ran into a reproducible crash that is restricted to a certain > > scenario. The crash occurs in QGlContextPrivate::syncGlState() when > > trying to call glDisableVertexAttribArray(). It seems the function > > pointer is not available. However, there are some other factors involved: > > Very wild guess, maybe remote desktop is somehow issuing a GL context > reset, and the code in question is not prepared to handle it? > > (Are we talking about QGL* classes here or QOpenGL* classes?) > This is (still) QGL..., we have not yet switched to the QOpenGL... classes. Remote desktop is definitely involved in some way, as its Windows 10 version supports OpenGL > 1.1. Probably the graphics driver also, as the issue is related to (older) Nvidia GTX boards. In the meantime we ran the OpenGL Extensions Viewer (version 6.0.5) both locally on one of the affected machines as well as via RDP. Over RDP, it also crashes, during "Querying properties - Forwarding context 4.1" or "... 4.3". So, the root cause seems to be unrelated to Qt (I assumed that earlier), but it would be nice if we could get our application / Qt 5.12.x to cure the symptoms, as at least Qt 5.6.2 did not trigger the crash... 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: Dr. Frank Heimberg, Jürgen Kesper ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Strange issue with Qt, OpenGL and remote desktop
Il 24/10/19 17:57, Rainer Wiesenfarth ha scritto: We ran into a reproducible crash that is restricted to a certain scenario. The crash occurs in QGlContextPrivate::syncGlState() when trying to call glDisableVertexAttribArray(). It seems the function pointer is not available. However, there are some other factors involved: Very wild guess, maybe remote desktop is somehow issuing a GL context reset, and the code in question is not prepared to handle it? (Are we talking about QGL* classes here or QOpenGL* classes?) HTH, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts smime.p7s Description: Firma crittografica S/MIME ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Strange issue with Qt, OpenGL and remote desktop
Has anyone of you experienced application crashes when running a Qt application that uses OpenGL over remote desktop on Windows 10? We ran into a reproducible crash that is restricted to a certain scenario. The crash occurs in QGlContextPrivate::syncGlState() when trying to call glDisableVertexAttribArray(). It seems the function pointer is not available. However, there are some other factors involved: - the crash happens *always *when the application is run over a remote desktop connection, but *never *if run on the same machine directly - the crash happens *always *with the application linked to Qt 5.12.4 (or .5), but *never *when linked to Qt 5.6.2 - the crash is restricted to two machines (out of a larger pool), one with a GTX 560, the other with a GTX 745 graphics card - all machines we used in testing are running Windows 10 Enterprise 64bit, with different versions (1803 to 1903, but all updates installed) - installing the latest available Nvidia drivers does not solve the issue We would be happy to hear of any comparable issue, ideally together with a solution for it... :-) 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: Dr. Frank Heimberg, Jürgen Kesper ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
