Qt 6.8.0 seems to have memory issues
-
wrote on 11 Oct 2024, 15:13 last edited by
I use multi-line build，if the loader switches too frequently or if too many projects are loaded or destroyed at one time, the memory will be exceeded or an exception will not be captured directly, the page will freeze directly or become unresponsive (stackview cannot be pushed). If you use Mediaplayer, this problem will occur more frequently and autoPlay will also fail. It is normal in 6.7.2.Is there any way to fix it?
-
I use multi-line build，if the loader switches too frequently or if too many projects are loaded or destroyed at one time, the memory will be exceeded or an exception will not be captured directly, the page will freeze directly or become unresponsive (stackview cannot be pushed). If you use Mediaplayer, this problem will occur more frequently and autoPlay will also fail. It is normal in 6.7.2.Is there any way to fix it?
@LZHD said in Qt 6.8.0 seems to have memory issues:
there any way to fix it?
Provide a minimal, compilable example to reproduce the issue and report a bug afterwards if the problem can be reproduced.
-
wrote on 12 Oct 2024, 01:04 last edited by
What are the exact error messages in console?
You might try adding
target_link_options(<your target> PRIVATE -s MAXIMUM_MEMORY=1GB)
to your CMakeLists.txt -
wrote on 12 Oct 2024, 03:06 last edited by
I have tried enabling asynchronous, increasing initialization memory, and adjusting the maximum memory, but all have no effect. It is random and the browser console cannot capture useful errors. Sometimes it is memory access out of bounds at .wasm.QQuickDeliveryAgentPrivate:: Sometimes isUncaught RuntimeError: null function or function signature mismatch
at .wasm.QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) It is also possible that there is only uncaught
3/4