It looks like you’re encountering a common limitation with Eclipse Memory Analyzer (MAT) when trying to parse very large heap dumps. Although increasing the JVM heap size for MAT (as you’ve done with -Xms8192m -Xmx10240m) is a good first step, parsing an 11GB dump can still be challenging due to MAT’s inherent memory overhead and processing limitations on large files. Even with 80–90% of the dump size allocated to MAT, factors like object graph complexity, retained set calculations, and MAT’s own memory consumption during parsing can easily cause it to run out of memory. A few suggestions you could consider: Try increasing the MAT JVM memory allocation further if your system allows it (e.g., -Xmx16384m). Ensure MAT’s 64-bit version is being used. Use the ParseHeapDump.bat script, but adjust its -Xmx value to match or exceed your new allocation. As an alternative, you might want to try other tools optimized for large dumps like HeapHero or IBM HeapAnalyzer. You can also consider splitting the dump (if possible) or analyzing it on a higher-memory machine. Large dumps often require tuning beyond just VM options — it’s also about available system memory, disk IO, and MAT’s parsing efficiency. If you’d like, you can share the dump file (if feasible) or its profile metadata, and we’d be happy to help you validate it with other tools or approaches. Apart from this you try the tool HeapHero and try to parse very large heap dumps. This will also help you with analyzing the memory of large heap dump files. If HeapHero works better for your large dump analysis needs, it might also be a good time to evaluate which memory analysis tool is best suited for your environment and use case. You can refer to this blog: Memory Analyzer vs. Java Profiler: Choosing the Right Tool for Performance Debugging

now its failing due to: FAILED: v8_context_snapshot_generator "<>/python-3.8.1-rh7/bin/python3" "<>/qtwebengine/src/3rdparty/chromium/build/toolchain/gcc_link_wrapper.py" --output="./v8_context_snapshot_generator" -- <>/gcc-10.3.0-rocky8/bin/g++ -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -m64 -Wl,-O2 -Wl,--gc-sections -Wl,-z,defs -Wl,--as-needed -rdynamic -pie -Wl,--disable-new-dtags -L<>/rocky8/harfbuzz-11.3.3/lib64 -o "./v8_context_snapshot_generator" -Wl,--start-group @"./v8_context_snapshot_generator.rsp" -Wl,--end-group -latomic -ldl -lpthread -lrt -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lresolv -ljpeg -lpng16 -lz -lxml2 -lxslt -lm -lexpat -lfreetype -lfontconfig -lharfbuzz-subset -lharfbuzz -ldbus-1 -ldrm -lasound -ludev -Wl,--start-group -Wl,--end-group <>/qt/build/qtwebengine/src/core/Release/x86_64/obj/third_party/blink/renderer/modules/app_banner/libapp_banner.a: error adding symbols: Malformed archive collect2: error: ld returned 1 exit status

I see this is an old thread and I see several unresolved threads on this topic. I'm leaving this incase it helps someone else who ends up here. The solution was twofold for me. Go to File > Export Project and select Enable Python Generator. This will create a main.py. Make sure you pip install PySide6-DS Hope this helps someone.

Hello i am using WinCC OA to develop a qt application. WinCC OA has some custom elements which cannot be detected by squish for example a polygon. Squish is now not able to detect this element with the picker. I know the name of the element but as it is of WinCC OA internal i do not know the type: waitForObject( {"container": "container", "name": "POLYGON1","type": "???","visible": 1} ); How do i get this information? And what to use if unknown? Is there any other way? I mainly just need to click this element. Thanks a lot

Thank you 😊

Oh right, I forgot about that one. Depending on the content you can apply the same to rows. In any case, since your issue is fixed, please mark the thread as solved using the "Topic Tools" button so that other forum members may know a solution has been found :-)

@Max Ok, j'ai compris : en modifiant la taille de la fonte du QLineEdit inclus dans le QTimeEdit, ça fonctionne. Bêtement je prenais la police "f" du QLineEdit inclus, modifiais la taille de "f" et faisais QLineEdit->parent->setFont(f). Ici "parent" était de trop. En me relisant, j'espère que ce que j'ai écris est compréhensible... A+ Sylvain

@RokeJulianLockhart to the best of my knowledge, no. The first release of Discourse was in 2014 and the forum is several years older than that.