<![CDATA[If you are having memory allocation problems when using QtQuick with Windows CE, check QTBUG-26227]]>As the title says, I've just posted a bug report about a serious problem that happens
when using QtQuick with Windows CE devices.

I guess it's the same problem at the root of various issues about QML code allocating memory
and never releasing it:
"QTBUG-26227":https://bugreports.qt-project.org/browse/QTBUG-26227

If you are using Qt 4.8.2 or a previous version and notice memory is allocated by QML code but never released as should be, give a look at the bug report and at the proposed fix, it may solve your problem too.

]]>https://forum.qt.io/topic/17686/if-you-are-having-memory-allocation-problems-when-using-qtquick-with-windows-ce-check-qtbug-26227RSS for NodeFri, 10 Jul 2026 23:19:56 GMTTue, 19 Jun 2012 22:04:23 GMT60<![CDATA[Reply to If you are having memory allocation problems when using QtQuick with Windows CE, check QTBUG-26227 on Mon, 04 Feb 2013 17:18:06 GMT]]>Lately I rebuild some stuff using Qt 4.8.4 and discovered that the bug still exists.
It exists in 4.8.3, too.

The fixes added to the source code instead of "#undef rewind"
contained "# undef rewind" (blank spaces between "#" and "undef")
and it seems that VS2005 C++ compiler for ARM ignores that.

]]>https://forum.qt.io/post/150998https://forum.qt.io/post/150998Mon, 04 Feb 2013 17:18:06 GMT<![CDATA[Reply to If you are having memory allocation problems when using QtQuick with Windows CE, check QTBUG-26227 on Thu, 21 Jun 2012 06:54:39 GMT]]>Thanks for that I'll do a trawl through our compilation log and see if it's there. We're building using 4.7.4 so it might not show up in that release (fingers crossed).

]]>https://forum.qt.io/post/142241https://forum.qt.io/post/142241Thu, 21 Jun 2012 06:54:39 GMT<![CDATA[Reply to If you are having memory allocation problems when using QtQuick with Windows CE, check QTBUG-26227 on Wed, 20 Jun 2012 15:59:40 GMT]]>It was the first time I built Qt for Windows CE 5.0 for production devices (previously we were using only Windows CE 6.0).

At first I was having memory allocation errors I initially supposed were caused by the 32MB limit for data and program dlls, so i forced -Os in the mkspec for the target device and inserted qDebug() messages to generate an application specific execution log about what was actually going on, after i noticed program termination happened before reaching the 32MB limit, I started combing the compilation log to see if there was something suspicious besides the usual data truncation warnings and found that weird warning about rewind() macro substitution.

]]>https://forum.qt.io/post/142208https://forum.qt.io/post/142208Wed, 20 Jun 2012 15:59:40 GMT<![CDATA[Reply to If you are having memory allocation problems when using QtQuick with Windows CE, check QTBUG-26227 on Wed, 20 Jun 2012 07:07:39 GMT]]>Thanks for that!

Did you changed compiler settings to enable extra warnings, or just notice it during compilation? I think I'm going to go back and re-compile my WinCE DLLs and check a bit more carefully.

]]>https://forum.qt.io/post/142160https://forum.qt.io/post/142160Wed, 20 Jun 2012 07:07:39 GMT<![CDATA[Reply to If you are having memory allocation problems when using QtQuick with Windows CE, check QTBUG-26227 on Tue, 19 Jun 2012 22:15:33 GMT]]>Ooops, I sent the previous post a little too fast.
Of course, the problem happens only with Windows CE.

]]>https://forum.qt.io/post/142145https://forum.qt.io/post/142145Tue, 19 Jun 2012 22:15:33 GMT