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

QML profiler service sends memory events in wrong order

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2: Important
    • Resolution: Done
    • Affects Version/s: 5.12.0 Beta 3
    • Fix Version/s: 5.12.1, 5.13.0 Alpha 1
    • Component/s: QML: Tooling
    • Labels:
      None
    • Commits:
      8af9d69554065924f9c92b29dd09d08ba6650328 (qt/qtdeclarative/5.12)

      Description

      Consider:

      iimport QtQuick 2.1
      import QtQuick.Window 2.0
      
      Window {
          width: 800
          height: 600
          visible: true
      
          Component.onCompleted: {
              var dictionaryTable = {};
              for (var j = 0; j < 646900; ++j) {
      
                  var word = "a" + j.toString()
                  dictionaryTable[word] = null;
              }
          }
      }
      

      Run this through the QML profiler and notice that all the memory usage events are aggregated into one. This is because all the memory usage events are sent in one block from QV4ProfilerAdapter::finalizeMessages() when the batch overflows. When appending memory events we need to check if there is a next call event and if so, only append memory events until that one.

        Attachments

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

          Activity

            People

            Assignee:
            ulherman Ulf Hermann
            Reporter:
            ulherman Ulf Hermann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes