Reducing memory footprint

My watch face has 10 different possible watch face fonts. Loading the watchface for all devices apart from the VivoActive HR is fine. However I run out of memory on the HR.

So even if I dont load the other 9 fonts not used on the HR will they use up memory? Is there a way ensure they aren't included in the HR build of the app but still in my project?

I need to reduce the footprint somehow!

Without loading the HR specific font I've used up 53.1k out of 58k

The font itself is only 986 bytes but when I load it I run out of memory! Eh!? Surely I have 5k left!?

Also is it more effecient to use pngs that are aquare and to the power of two, iei 64* 64 as opposed to 62*62 or 128 * 32?

jim_m_58 over 8 years ago

A couple of things you can do, but involving resource overrides.

I'm guessing that not all the fonts are needed on all the targets, and if that's the case, don't even include them all for all targets. And then, you probably don't need all of them loaded in your app at the same time.

With build file excludes, you can also tailor the code based on the target device. For example, you don't need code for round targets if you're building for a va-hr.

Here's a thread about build file excludes with a simple sample:

https://forums.garmin.com/forum/deve...excludes-quot=

ruperthawkes over 8 years ago

I tried actually removing all the non HR font png/fnt and rebuild but it didn't make any difference to the memory usage - which is odd. As for excluding the code, there isn't anything in there particulary that just for non HR

I do just load the selected font for based upon settings. So only one is loaded at one time

Weirdly on the 735 without loading the font, I have 53/58kb memory. The font file is just 1kb but I run out of memory when I load it.

On the 935 which is exactly the same code / resources the memory usage is 56.2 so why wont that load into 58k on the 735?!

jim_m_58 over 8 years ago

When you say 56.2, is that your "peak" memory or just what you see on the bottom line of the sim? See the "file>view memory" selection in the simulator.

You may need to look at just "slimming down your code" a bit. There was a good breakout at the Summit that may help:

https://developer.garmin.com/index.php/blog/post/connect-iq-developer-summit-2017-breakout-effective-monkey-c

ruperthawkes over 8 years ago

54.6 peak

will check out the video, but I had realised that I had a fair bit of duplicated code which I've cleaned out and reduced memory by about 10kb