This looks like a null pointer crash on exit.* The main thread is processing global destructors. The render thread is presumably trying to use an object that has already been destroyed and set to null when QApplication was destroyed. (or destroyed by a global static destructor)
It seems like the render thread needs to be shut down cleanly before / during QApplication destruction. *The fault address of 0x8 suggests a load with offset from the null pointer. This could be trying to access the virtual function table or the d-pointer of a class. (I'm used to seeing 0x4 for null pointer calls to d_func() on ARM - 0x8 could be the same thing on x64) -- > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of Girish Ramakrishnan > Sent: 18 June 2012 16:41 > To: [email protected] > Subject: [Development] qtdeclarative CI > > Hi, > AFAICT, no changes are getting past the qtdeclarative CI. The last > integrated change was 5-6 days back. It's crashing on the Mac. It's now > crashed many times with the same backtrace (in > QQuickRenderThreadSingleContextWindowManager). > > https://codereview.qt-project.org/#change,28741 > https://codereview.qt-project.org/#change,28676 > > Girish > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development ________________________________ Subject to local law, communications with Accenture and its affiliates including telephone calls and emails (including content), may be monitored by our systems for the purposes of security and the assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
