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

ListModel doesn't keep objects of JavaScriptOwnership alive

    XMLWordPrintable

Details

    • All
    • 16fc4cf366961e50b5bdf29af5c0546fe3c69495 (qt/qtdeclarative/dev) d30fad2a71aa3dab8e858b5fd421f8103b1bdcac (qt/qtdeclarative/6.2), 718f3469f (dev), 749470e6b (tqtc/lts-6.2), 389110675 (6.5), a22ea1619 (6.4)

    Description

      The shown ListModel doesn't keep "o" alive, which is a QObject whose ownership is JavaScriptOwnership. I observe that "gc()" yields to a destructor call of the object that "o" references.

      Please use the attached "gc" tarball that contains an example project. Entering Code doesn't appear to work in the Description.

       

      Attachments

        1. gc.tar.gz
          2 kB
          Johannes Schaub

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-99279 listModel.set() leads to crash in some situation.

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-95895 REG 5.15 -> 6.2: destroy() does not destroy objects after appending listModel.

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-80589 Assigning a new QObject w/o a parent to a C++ property through QML doesn't prevent it from being garbage collected

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ulherman Ulf Hermann
              jschaubzes Johannes Schaub
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: