OS Simulator 0.9.1 memory management

[Guy_]

Is there a more stringent control of memory in this version?

Builds that actually load fine on watches won't load due to an out of memory error on this version.

In passing, it would be nice if the running build could be highlighted in the Apps tab in a future update.

[Gondwana]

Previous versions of the sim allowed double the amount of memory than the actual device being simulated (because sim code was larger than device code). I'm not sure this is still true for sim 0.9.1, which would explain what you observed.

[Guy_]

The issue seems to be connected with the changes in SDK 4.3 from 4.2 implementation, possibly from the change to the FS import.

The way the OS simulator is handling 4.2 and 4.3 code may be different than before, but it remains that the same FBA code loaded fine on a watch, now won't load in the simulator and it may need researching as to why. The code was previously tested in the Simulator.

It also seems that code generated in version 4.3 is at least 10 % bigger than for version 5.0, using the same source.

As 4.2 is no longer available it cannot be verified if this is a new issue or pre-existing one.

But the result is that freshly built code won't load on the watch or in the Simulator anymore, if the project is quite big, for the older watches.

This may be an additional issue with the new versions of the Simulator and Studio.