Simulator Bug: Clears Memory after Sending Settings

Again, it depends on how complex your setting are.  Not only number of settings, but the size of a setting.  If you have only 1 setting but it allows a 2k string, that could do it, or 20 settings of 100 bytes each, or 100 settings of 20 bytes each

Again, it depends on how complex your setting are.  Not only number of settings, but the size of a setting.  If you have only 1 setting but it allows a 2k string, that could do it, or 20 settings of 100 bytes each, or 100 settings of 20 bytes each

Will do, and only 11

Instead of using properties for everything, use storage where it makes sense.  Unless it's something that the user can change with settings, it really doesn't need to be a property but can just be in local storage

What is your total for properties?

Yes

are you mixing properties with settings and properties without settings?  

One thing to try is switching to a target with a larger sized (memory wise) data field, and see what peak is there after changing settings

A fr245 has the 28.6k max, while a 245m has a max of 60.6k for example