On segunda-feira, 9 de setembro de 2013 18:10:25, Benjamin Zeller wrote: > > 2) there's a lingering bug in the dispatcher that causes it to send events > > to objects that have recently been moved away. For example, it's possible > > that the event dispatcher got woken up by two socket activities. When > > handling the first, you pushed the second socket to another thread. When > > you resume the event loop, the dispatcher still tries to handle the > > second socket, which has now been moved. > > It's very likely that there are lots of other socket events, i'm > currently doing a stresstest on the server application, lots of > requests and connections are opened. Also this does not happen all the > time, just on high loads and even then not always. But it always crashes > at the same places, in the worker thread and the main thread.
Can you try the same test with QT_NO_GLIB=1 in your environment? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
