Out of Memory ///// Out of CPU ??? ?

Hello, 

Recently one of my applications has been getting bigger and bigger, and now approaches the point where I have about 128 kB  of memory use when it is running.

I have noticed now when going through the simulator that several watches fail due to not enough memory which is fine, but I have also noticed 

Those with 1275 Kb seem to run the app fine

Those with less than 1275... like the Forerunner 745 / Venu 3 / Venu 4 / with supposedly 1019Kb, do not appear to complete on compute functions for some reason.

They don't fail, they just don't seem to update some of the navigation dependent figures, I have no idea what's going on ? Is it something to do with the CPU chip ?

Maybe this list will help:

Forerunner 245  / 265 / 645 / 745 / 935 does not have enough memory / CPU to support the app any more. 
Vivoactive watches ( 3 and 4 ) , they boot but compute info so missing information ( track data ) 
Venu / Venu SQ not enough  memory
First Avenger - not enough memory
Fenix Chronos - Not enough memory  
Fenix 5 / quatix - not enough memory
Fenix 5S - not enough memory
Approach S62 - missing data calculation
Captain Marvel  - missing data calculation
Darth Vader  - missing data calculation
What Works in the watch simulator( I just tested  the 1275kB watches)  : 
FENIX 5 Plus  good
Fenix 5X good
Fenix 6 plus or PRO / tactix / delta X good
Forerunner 945 - Good
MARQ watches - Good
D2 Charlie / Delta / Delta PX / Delta S - Good  
Descent Mk1 - Good
Square displays:  ( not optimised )
GPS Mapp 86 - good ( not optimised )
GPS Mapp 66  - good  ( not optimised )
Montana 7 series -  good   ( not optimised )
Oregon 7 series -   good   ( not optimised )
Rino 7 series - Good  ( not optimised )
Edge Explore - Good  ( not optimised )
Edge 520 plus - Good  ( not optimised )
Edge 530 - Good  ( not optimised )
Any ideas?
  • I use activity info Track - to give me the True north referenced Track of the watch ( not the heading )  - I use it for all kinds of things - as a compass , to calculate VMG ( velocity made good ) to a point that you are not pointing directly at.... It's been working for 2 years now without issue, but now maybe because the app is bigger, it stopped working on some watches. Is the watchdog a function of the computing power of the watch model? and that's why the Pro models and X models seem to have no issue, but now all  non mapping models almost cannot do the calculations ? 

  • To answer this Question I am not because my APP uses Relative Navigation.

    For example - If I have a waypoint selected, then my waypoint calculations are all in True, and then it compares my current True track to the waypoints true track, and gives the user Relative angle ( Turn 60 degrees left to go to the waypoint ) for example. 

    I also use the same thing for Wind, so the user saves the True angle of the wind at the start of the session - this is compared to the True Tack during the session, and I can give them relative information ( Wind axis is 40 degrees right of where you are going ) etc., I can calculate Velocity made good directly towards the waypoint or wind axis when the user is pointing away from it using relative numbers..

    No conversion to magnetic necessary at all.