@JKSH Yes I did.

On QT part, we followed a lot of techniques mentioned in that post. Using Loaders for lazy loading, optimizing images, using qtquickcompiler. The major challenge is on the OS boot time that we are working on.

Just by loading one page and coming back, we can't make out the memory leak. Try multiple times like this. If you see a increase & no decrease then we can conclude memory leak. If you can send me the complete example, we can try as well.

Hi Junajex,

Could you mark this topic as solved (topic tools on the bottom right > marks as solved)

Thanks,

Eddy

I appreciate your response, it lead me to a lot of research on the topic! I figured out it was much easier to implement a tabview on the main view and then to connect the signals with the child objects which were themselves individual views.

@Mark81 The example works. Is there anything else that is missing ?

Ha I know the feeling, like me before, thinking ".. that stupid Qt, why doesn't this work, why are they so dumb..." oooh, it helps to run qmake again :-)

Expose your component through a property of file's root item.

Because you didn't ask a question. Use the button to "Ask as question" and then you'll have the "Mark as solved" that should appear.

@kshegunov
Yap, Thanks, Thanks. :-)
Now It's generate all the required files, I also need to add QWidgets in Select Required Models.

Best Regards,
IL

@kylecorver Can you post the complete program? The original isn't a a valid Qml document, leading to guessing about which errors will or will not occur. The OS and Qt version used might also be relevant.

Maybe

//main.qml: import QtQuick 2.5 Loader { id: loader source: "MyComponent.qml" onLoaded: { loader.item.property1 = "secret" loader.item.property2 = 777 } } //MyComponent.qml: import QtQuick 2.0 Rectangle { id: rect property string property1 property int property2 TextEdit { id: text_edit anchors.centerIn: parent text: property1 + property2 } }

or

//main.qml: import QtQuick 2.5 Item { id: main width: 200; height: 200 property string property1: "secret" property int property2: 777 Loader { id: loader source: "MyComponent.qml" onLoaded: loader.item.text = property1 + property2 } } //MyComponent.qml: import QtQuick 2.0 Rectangle { id: rect property alias text: text_edit.text TextEdit { id: text_edit anchors.centerIn: parent text: property1 + property2 } }

or

import QtQuick 2.0 Rectangle { id: rect TextEdit { id: text_edit anchors.centerIn: parent // rect.parent -> loader; rect.parent.parent -> Item with id 'main' text: (rect.parent.parent.property1 !== undefined) ? rect.parent.parent.property1 : "" } }

https://bugreports.qt.io/browse/QTBUG-48053

@shav

When I call setSource() method the old content removed from memory and all connects to signals is removed?

AFAIK, Yes.

I know this is marked as solved, but just as an aside: to do this with a Loader, you could use a Settings object to store the properties that should be reset to restore the state of the user's view - still a Labs feature just now, but it works very nicely.

@Maxim-DC Yes it is possible. You can find an example here. The exact file in it where it is used.

hello,

can you tell us how you solve your problem?
thank you.