Higher memory usage with SDK 3.2.1

Did you add anything, say anti-aliasing?  This is one reason you never want to be too close to the edge, memory wise.

No code changes, simply compile and run the same code in the simulator and you get a higher memory drain for all devices.

Someone like Travis.ConnectIQ can say for sure, but it could just be a increase due to 3.1/3.2 differences.

At this point I honestly do not know where the memory increase is coming from. This is interesting, and if I have some time I'd like to dig into it.

Possibly some base classes you extend have new member variables, which would increase the ram consumption.

You can compare before and after in detail with "View Memory" tool in simulator, to see which part has increased in size.

It sounds like he's doing an apples-to-apples comparison with the same app compiled and run with one version of the SDK versus a more recent version of the SDK. If this is the case, it is most likely not a change to the app code that is causing the problem.

My initial guess is that adding new API classes/functions has an impact on memory use. Only a bit of testing tell.

Right, this is what I also understood, and suggested that some change in base classes (API classes from SDK) between SDKs is causing the memory increase.

It's like Travis said... apples-to-apples comparison with the same app compiled and run with version 3.1.9 of the SDK versus the new version 3.2.1 of the SDK.

I also get a larger IQ file with the export wizard and the new SDK.

In previous releases the memory keeps the same or event gets better same for the exports.

TheMagician said:

I also get a larger IQ file with the export wizard and the new SDK.

This is likely unrelated. If we added another part number for an existing device, the .iq file generated with the newer SDK will have another set of files to allow it to support the new part number.