Closed JosephAbbey closed 8 months ago
Further testing is revealing memory limits. The widget fails when the application works. The simulator shows us the memory limits as follows.
The widget is now using 56 of 59.9 kB and crashing. (Game not over yet)
Using a script to ensure compilaion of Vivoactive 3 without debug (--release) and deploy to the simulator we have 52.4/59.9 kB used.
Changing the JSON configuration to a simpler one (sill using no debug) we have 49.0/59.9 kB used.
So we have confirmation that the JSON configuration can cause this device to run out of memory. Not an unexpected result, but we are clearly "on the edge".
Latest commits provide a saving by removing the menu style option and associated class:
Vivoactiove 3 Widget with template menu items (previously failing on watch) now 50.9/59.9 kB
Latest commit now 50.4/59.9 kB 52.5 kb after updating status menu items.
Runs on vivoactive3 without memory issues