Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-59760

Calling QEventLoop::exec(ExcludeUserInput) causes a busy loop with 100% CPU usage on glib

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 5.9
    • 5.6.2, 5.7.1, 5.8.0
    • QPA: X11/XCB
    • 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

          Bug - A problem which impairs or prevents the functions of the product. 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.

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-57101 QFileDialog does not work when run inside an QEventLoop with ExcludeUserInput set

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Closed
          For Gerrit Dashboard: QTBUG-59760
          # Subject Branch Project Status CR V
          190785,7 Prevent busy loop in glib event dispatcher 5.9 qt/qtbase Status: MERGED +2 0

          Activity

            People

              paeglis Gatis Paeglis
              apollo13 Florian Apolloner
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes