QNX: Fix crash due to re-entering QToolTip::show().

The flushWindowSystemEvents() was added to send the geometry
event synchronously. A side effect was that all input events were
also sent.

We don't want that. We're probably in setGeometry() because some
other input event brought us here, and it's still in the call
stack.

One crashy example is the static method QToolTip::show() which
uses static variables([1]). If we process input events while the
first QToolTip::show() is still on the call stack, it will trigger
a second one, deleting stuff ([1]) that the first invocation will
still need once the stack unwinds.

Change-Id: Iea22419a7f386d6b6231404666092340dfd1afed
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
bb10
Sergio Martins 2012-11-21 09:52:05 +00:00 committed by The Qt Project
parent 23ea027841
commit d429d65628
1 changed files with 6 additions and 2 deletions

View File

@ -179,9 +179,13 @@ void QQnxWindow::setGeometry(const QRect &rect)
m_platformOpenGLContext->requestSurfaceChange();
}
// Send a geometry change event to Qt (triggers resizeEvent() in QWindow/QWidget)
// Send a geometry change event to Qt (triggers resizeEvent() in QWindow/QWidget).
// Calling flushWindowSystemEvents() here would flush input events which
// could result in re-entering QQnxWindow::setGeometry() again.
QWindowSystemInterface::setSynchronousWindowsSystemEvents(true);
QWindowSystemInterface::handleGeometryChange(window(), rect);
QWindowSystemInterface::flushWindowSystemEvents();
QWindowSystemInterface::setSynchronousWindowsSystemEvents(false);
// Now move all children.
if (!oldGeometry.isEmpty()) {