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

Check if QWidget::setWindowTitle() can be optimized

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Out of scope
    • Icon: P3: Somewhat important P3: Somewhat important
    • None
    • 4.7.2
    • None

      In a recent trace we noticed that QWidget::setWindowTitle() (called my
      MApplicationWindow) needs more than 200ms. In the end it turned out that this was a corner case and normally the
      call needs ~15ms.

      The problem lies in qstring_to_xtp() in qwidget_x11.cpp. It seems as if the
      call to QTextCodec::codecForLocale() does blocking X calls
      _XlcResolveLocaleName and _XlcRCreateLocaleDatabase. If X is busy with
      something out whole app is blocked.
      Do we really need these calls? In the code we find this comment:
      // ### If we knew WM could understand unicode, we could use
      // ### a much simpler, cheaper encoding...
      I guess mcompositor understand unicode, doesn't it?

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            earthdomain Earth Domain (Inactive)
            jupakari Juuso Pakarinen
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes