Problem with app properties suddenly using up lots of memory?

Has anyone come across a problem when running an app in the simulator (a watchface) that when they add one new property then the memory used by application settings in the simulator suddenly increases massively?

I don't even need to add the property as a setting for this to occur. And if I remove that property (or even a different property) then the memory usage suddenly drops back to normal again.

Maybe I am hitting a soft limit of some kind? I currently have 102 properties and the problem seems to occur when I go to 103 properties.

In the simulator memory usage view my normal <Application Settings> size is 2384(3949).

When I add the one extra property then the <Application Settings> size jumps to 9404(10981) by more than 7k!

And this has the unfortunate effect of making my watchface stop working when I try and change settings from the settings editor as there is no longer enough memory available in the app!

jim_m_58 over 7 years ago

Which SDK and target? The latest SDK is 3.0.8

Please post your properties.

markdotai over 7 years ago

I am on 3.06 - so I'll try and update to the latest.

Targeting 3.0.x

Attached is my properties file though for now.

markdotai over 7 years ago

The same thing still happens for me with 3.0.8 unfortunately. Does it sound like a bug?

jim_m_58 over 7 years ago

Do you mean it rises when you change settings (The App Settings editor), or just get larger when you add it to the xml?

markdotai over 7 years ago

The increase in memory usage occurs just by changing the properties xml file and running the app again - the increased usage is visible immediately right from the start. I don't need to change the settings via the App Settings Editor (I know that increases the peak usage as well even further).

jim_m_58 over 7 years ago

Nothing jumps out at me in the xml. How are you seeing the memory increase? What's your peak memory before the new property?

What device is the target you are using?

markdotai over 7 years ago

Tried targeting Fenix 5, Fenix 5 plus, Fenix 5s plus, Fenix 5x, Fenix 5x plus, Forerunner 935
Immediately after running I open the memory view for the info and they all come up almost exactly the same:

With 102 properties: current mem = 73.0kB, peak mem = 76.2kB, <Application Settings> size = 2384
With 103 properties: current mem = 79.9kB, peak mem = 83.1kB, <Application Settings> size = 9404

So there is that 7k difference. <Application Settings> size is exactly the same on all of them.

jim_m_58 over 7 years ago

I'd do a thread in the Bug Report forum. Maybe include a bare-bones app (like the eclipse WF template - File>New>CIQ Project>Watchface) with your set of properties that demonstrates it.

I suspect it has something to do with having 100+ properties - do you have settings for all of them, or are there some you can move to Application.Storage?

bine8x8 over 7 years ago

I have the same problem - when adding one property to the xml file, the settings no longer apply. When this property is removed from the xml file, the settings are restored. I reported this in the bugs report. I did not count the exact number of properties, but this number is greater than 100.

GHG23 over 7 years ago

I also expercienced this. It force me to split a datafield in two datafields; one for the watches with 32kB available for datafields and one for watches with 64 or 128KB available. I also saw that although the extra resources aren't used by the 32kB watches, the memory usage for those watches still increased.