@GrecKo No the caller list just lists one unresolved function. I tried cross compiling the UI with debug symbols to run on my embedded system with heaptrack but I got the same result. [image: 5b952860-caa1-4b4c-b12c-7cc14ecface7.png] I tried running Valgrind on it too but I think to make that really work I need to setup a native Linux Qt development environment. I already tried that but I did it in a VM and it was weird. Open street maps had no issue with ram it was steady on the Linux VM. But Maplibre wouldn't run and I suspect its the VMware graphics drivers causing it to fail to start. I did change something that I believe had a huge impact. My map was a singleton and I tried just putting the map straight into the qml and it seemed to really reduce the memory growth. I'm not sure what to make of it. On Windows this is what I'm seeing now with the Private Bytes. Though from what I've read this isn't really a good indication of a memory problem but it does look kind of linear. [image: 34694ac0-0356-413b-aff4-48164be50e45.png]

@Axel-Spoerl is there any way we could get some kind of usage statistics? For example the % of people using QML, QWidgets or both? Not sure if such a thing is actually tracked. I would imagine yes, to determine future development investments at Qt. But it would be really cool to know this, especially a back then to now comparison!

In QDS, SVGs usually look blurry when the path is being scaled instead of rendered at its native size. Make sure the SvgPathItem matches the original SVG viewBox and avoid scaling it down inside the component. If possible, import the SVG as a file and use an SVG Image element rather than pasted path data, and keep width/height proportional to the source. This prevents QDS from rasterizing it at a low resolution.

Found it. I overlooked the following traceback in the logs. Traceback (most recent call last): File "/mnt/ssd2/develop/experiments/python-squish/mysquishtest.py", line 16, in <module> squishtest.waitForApplicationLaunch() RuntimeError: Waiting for application timed out When I remove the call squishtest.waitForApplicationLaunch() it works and I can use squishtest.test.compare() to test conditions.

Hi everyone, We work on developing enterprise learning and training platforms, and recently we’ve been exploring Qt for building desktop or device-based applications that support safety training use cases. In industries like oil & gas—especially in regions such as the UAE—safety training systems often need to support offline access, structured learning modules, controlled user roles, and reliable performance across different environments. We’re interested in understanding from the community: Has anyone used Qt for building training, compliance, or safety-related applications? How well does Qt scale for enterprise-focused learning or content-driven platforms? Any best practices or architectural considerations when using Qt for regulated industry use cases? This is mainly an experience-sharing and learning discussion. Looking forward to hearing your insights. Thanks!

Added a new topic that refers to this one, providing an implementation of the owner's code expressed in Qt Task Tree: https://forum.qt.io/topic/164406/qt-task-tree-in-action

[image: 0cfb10bf-f94f-40b2-8b98-bf5d24531786.png] [image: 537eeaa5-d72a-49e5-a68b-2e3c8503066e.png] [image: 72ea1952-2512-45dc-9328-ba748637d0b1.png] [image: 8515b760-6fb0-49e8-859b-025e1a29d570.png] [image: 70e54bb7-615c-4674-9f8e-4e6545063587.png] [image: 571b47b9-d179-438f-86c8-5c74845c62ff.png] Voici pour la partie programmation

Hi, This is a user forum. You should open a feature request on the bug report system.