"Jump" in memory allocation for every 16th extra string user setting - huh?

Hr. Mortensen said:

Here is an example XML file with settings demostrating this. Here I have added comments on how much each of the many bottom string proporties adds of memory allocation (I added them one-by-one, ran it in simulator, and used System.println(System.getSystemStats().freeMemory) to see the diff in added memory):

Might help if you look at the object size in the simulator's memory viewer, so you can try to pin down exactly what's changing, down to the last byte.

I suspect that it's something like they want to avoid an allocation for every string, but instead grab enough for 16 objects at a time

jim_m_58 said:

I suspect that it's something like they want to avoid an allocation for every string, but instead grab enough for 16 objects at a time

If that were the case, seems that the next 15 properties after each jump would consume 0 bytes each.

Not if memory was required for the object itself,  Think of an array,  You have an array, but with simple objects it doesn't take more memory, but of you put a complex object in an array, it does.

I'm very sure - good tip on using letters!

good input - I have now analyzed this using the sim memory viewer! Made an analysis with ID's 1-18 vs 1-19. So, difference vs adding just one more string. Hope this image is viewable:

So, clearly, there is a jump in the overall settings allocation, not coming from a single setting ... 

Sounds like something worth to report as a bug, but before that can you test it in real device by logging the free memory in both cases (18 vs 19) so to know if the bug is only in the sim or also on actual devices?

I have now tested on my fr645 - and also on the real device the difference from adding the one extra string from 18->19 is 352 bytes! So, it's not a bug in the simulator....