Details
-
Bug
-
Resolution: Invalid
-
P2: Important
-
5.15.3
Description
When an Object with JavaScriptOwnership is accessed in QML, it results in a memory leak.
Please refer to the sample attached, you can see the Foo's destructor is not called. If any of the commented lines is commented, it works fine.
Bar{ id: bar // Assigning myFoo.counter solves the issue // property int name: myFoo.counter myFoo.counter:7 // Printing myFoo.counter solves the issue // Component.onCompleted: console.log(myFoo.counter) }