• Replies 5 replies
  • Subscribers 18 subscribers
  • Views 936 views
  • Users 0 members are here
Options
Related

2.3.0.beta1 requires more memory than 2.2.6

peterdedecker
I've noticed that the 2.3.0.beta1 has a higher peak memory than previous iteration(s), the screenshot below is from my simple datafield "FatBurner" (which doesn't contain all that much logic really).
I've noticed the same behaviour in my other apps as well (in my Pacer app I even got an out of memory error on the fenix3, because I programmed up until the edge of what was possible with peaks in 2.2.6 up until 15.8k)

you can say that 200-300 bytes more memory consumption is not a lot, but in the tight memory limits the apps have to operate it would be preferrable that new iterations of the SDK use the same (or less) memory than previous iterations.



upper line = screenshot after starting the app
lower line = screenshot after simulating data and pressing start


edit: could be a fitcontributor thing, a freshly generated simpledatafield does not require more memory, but for instance the sample app "MoxyField" establishes the same behaviour of requiring more peak memory in the new sdk
  • Former Member
    Former Member
    Hey,

    Thanks for reporting. I wasn't able to reproduce what you were seeing exactly. I did see inconsistencies, but I was actually having a drop in peak memory. I've created a ticket to investigate which is correct and what the intended behavior here is.

    Thanks,
    -Coleman
  • I can confirm that 2.3.1 uses less memory than 2.3.0.beta1, no out of memory errors here...

    On a sidenote it's rather annoying that the peak memory value now has to be checked through "View Memory" as it's no longer available in the status bar of the simulator...

    Feature Request: Could you create a ticket to reinstate the peak memory value in the status bar (or in case it's not wanted to have it there all the time, to provide an option to show the peak memory value there?)
  • ... it's rather annoying that the peak memory value now has to be checked through "View Memory" as it's no longer available in the status bar of the simulator...


    I support that view...why would they relegate such a useful feature?
  • It's probably because they added new stats and all of them won't fit in the bottom line of the sim for all targets - object usage and peak object usage.

    The object info has been request often over the last couple years.
  • We added the ability to double-click the basic memory stats in the sim window to display the memory viewer, so hopefully that helps mitigate some of the hassle when checking peak memory.