Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.6.2, 5.7.1, 5.8.0
-
None
-
Ubuntu 16.04
Debian unstable
CentOs 7
Description
Starting this simple testproject: https://github.com/apollo13/qt_bug_glib and clicking on the "trigger" button immediately causes 100% cpu usage. If one exports QT_NO_GLIB=1 cpu usage stays down.
Assigned to QtGui since thiago said that this is not a QtCore issue.
Attachments
Issue Links
- relates to
-
QTBUG-49770 Native Gtk2 file dialog (and possibly any other native dialog) can come up in a broken state when opened after a QCoreApplication::processEvents(QEventLoop::ExcludeUserInputEvents) call.
- Closed
-
QTBUG-57101 QFileDialog does not work when run inside an QEventLoop with ExcludeUserInput set
- Closed