Maximum amount of Offline Trend Macros on Windows CE
If an uBrowser for Windows CE is used, the maximal amount of Offline Trend Macros is limited by the available memory. In versions up to uBrowser version 1.5.12.092c, this limitation is hardcoded in the uBrowser executable. For these versions, no more than 35 Offline Trend Macros are recommended (depending on the amount of containers and HTML tags).
If too many Offline Trend Macros (more than 35, depending on other factors like the amount of HTML Tags and Containers) are used in one Web Editor project, the uBrowser does not run correctly. Instead of properly showhing the project, the error message similar to: "!!! MU_alloc2(2) failed, 524290 > 524288" is shown in a command prompt that is opened automatically. On the Micro Browser, the PPO values are not shown but the message "No component selected" instead.
The reason for this problem is that the allocated "heap 2" memory is not sufficient. In this memory area all containers and HTML tags are stored and until version 1.5.12.092c the size of this memory is hard coded to 512 kBytes. Because every Offline Trend Macro does create 5 containers of 2 kBytes each (--> 10 kByte per macro), an amount of more than 35 to 40 Offline Trend Macros can be critical.
Either reduce the number of used Offline Trend Macros in your Web Editor project or use a uBrowser.exe version higher than 1.5.12.092c. The version 1.5.12.092d has an increased size of 4 MBytes for the heap2, and later versions will provide the possibility of configuring the heap in the configuration file.
For performant panels like Celeron based ones, another workaround could be using the Appletviewer of the Internet Explorer. This workaround works because there is no limitations of the size of memory where the containers are stored if the applet is shown by e.g. the Sun JVM.
PCD7 / D5xxx (Windows CE)
Last update: 27.05.2015 05:01
First release: 10.01.2008 08:49