Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-32062

QML profiling randomly fails to start on minGW environment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P2: Important P2: Important
    • None
    • Qt Creator 15.0.0-rc1, Qt Creator 16.0.0
    • QML Profiler
    • None
    • win-MinGW13.1.0-Windows11-23H2-x64 + Qt Creator 15.0.0-rc1/16.0.0-beta1 + Qt 6.8.1
    • Windows
    • 5ec07b368 (master)

      Squish test tst_simple_analyze randomly fails on win-MinGW13.1.0-Windows11-23H2-x64 target. Other targets(linux-g+-Ubuntu22.04-x64, linux-g+-Ubuntu24.04-arm64, macOS-clang-14-x64, win-msvc2022-Windows11-23H2-x64) are working fine.

      Test steps:
      1. Create a new 'Qt Quick Application'
      2. Paste following code to Main.qml

      import QtQuick
      
      Window {
          width: 640
          height: 480
          visible: true
          title: qsTr("Hello World")
      
          Timer {
              property int runCount: 0
              interval: 2000
              repeat: true
              running: runCount < 2
              onTriggered: {
                  runCount += 1;
                  var i;
                  for (i = 1; i < 2500; ++i) {
                      var j = i * i;
                      console.log(j);
      
                  }
              }
          }
      }
      

      3. Select 'Debug' from the sidebar
      4. Start 'QML Profiler'

      Result:
      'QML Profiler' randomly fails to start. Hitting the 'Stop' button stops the 'Elapsed:' timer, but 'Stop' button is still active and 'Profiling application' message is displayed. Restarting Creator and repeating test steps might fix the issue.

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

            ansemkiv Andrii Semkiv
            jukkanokso Jukka Nokso
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes