Complete

This is by design.

The settings are being serialized to send to the simulator or phone.

opening settings editor consumes app memory

sdk 4.0.7
eclipse CIQ plug in: 4.1.0.beta1
eclipse ver: 2021-09 (4.21.0) Build id: 20210910-1417
windows 10
watch face
minSdkVersion 2.4.0

CASE 1

wf starts, peak memory 88.0

[ecilpse][app settings editor] - open only window and choose project (no push any buttons), peak memory 90.0

CASE 2

wf starts, peak memory 88.0

[simulator][property data]  - open only window (no push any buttons), peak memory 90.0

In both cases there is no calls for app.onSettingsChanged, settings data exist in memory so there shouldn't additional memory consumption.

Now, when you have e.g. 90.5 kB used from 92 there is an error "unable to serialise data" or "out of memory exception" if i choose OK in setting editor.

Parents
  • I have been unable to reproduce this issue. I am running on a beta2 plugin. That is the only thing different, but I've tried loading up one of our WFs with app settings. I watched the peak memory usage and when I opened the app settings editor the memory stayed the same. There was no increase either when I pushed changes through the same menu. I did see an increase in memory when I went into the app settings via the sim > "Trigger App Settings".

Comment
  • I have been unable to reproduce this issue. I am running on a beta2 plugin. That is the only thing different, but I've tried loading up one of our WFs with app settings. I watched the peak memory usage and when I opened the app settings editor the memory stayed the same. There was no increase either when I pushed changes through the same menu. I did see an increase in memory when I went into the app settings via the sim > "Trigger App Settings".

Children
  • sdk 4.0.9

    - app starts, change to low power  - I don't read settings during low power
    --memory usage 70.3, peak 71.1, app settings 1.369
    - [eclipse][qonnect IQ][App settings editor], choose from combo only app that run in sim
    --memory usage 70.3, peak 73.5 <-------- + 2.4kB
    - [send settings] without any changing
    -memory usage 70.3, peak 74.4  <-------- + 0.9kB
    - exit from low power reading settings
    -memory usage 70.3, peak 74.4 - didn't change because probably below previous peak