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

QtQuickControl BusyIndicator performance regression

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P1: Critical P1: Critical
    • None
    • 6.8.2
    • Quick: Controls 2
    • None
    • All

      Adding BusyIndicator in a QML project cause missed frames and general sluggishness, at least when doing GLES rendering.

      The performance regression occurs as soon as the BusyIndicator is in the "running" state, even if it is not visible.

      To reproduce this issue, run the sample openglunderqml, after adding this in the main.qml:

      import QtQuick.Controls.Material

      Item {
            visible: false
            Repeater {
              model: 10000  // adjust this number for your configuration
              BusyIndicator

      {             running: true  // set to false to get normal performances again         }

            }
          }

       

      The rendering run smoothly with Qt 6.6.3 (60 FPS) but just a few FPS with Qt 6.8.2

      A work-around is to add the binding "running: visible" in the  BusyIndicator so that at least hidden BusyIndicators stop impacting the whole app performances.

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

            qt.team.quick.subscriptions Qt Quick and Widgets Team
            xalioth Fabien Chéreau
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                There are no open Gerrit changes