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.

_psx_
Parents

  • sdk 4.0.7
    eclipse CIQ plug in: 4.1.0.beta2 <------------------- new SDK
    eclipse Version: 2021-12 (4.22.0) Build id: 20211202-1639 <----------- new eclipse
    windows 10
    watch face
    minSdkVersion 2.4.0

    and now I can see strange behaviour of settings

    - app starts 54.8kB

    - run [app settings editor] from eclipse, do nothing and save

    - mem 54.3kB

    this for case when device has own settings/properties  than default

    it means that ciq has in memory all settings and then user try to change settings there is merging and delete unused

    I prepare different scopes of settings for devices to save memory  but  you can see it is waste of time if user can't change settings and it default when user setups app (nobody change settings everyday.)

Comment

  • sdk 4.0.7
    eclipse CIQ plug in: 4.1.0.beta2 <------------------- new SDK
    eclipse Version: 2021-12 (4.22.0) Build id: 20211202-1639 <----------- new eclipse
    windows 10
    watch face
    minSdkVersion 2.4.0

    and now I can see strange behaviour of settings

    - app starts 54.8kB

    - run [app settings editor] from eclipse, do nothing and save

    - mem 54.3kB

    this for case when device has own settings/properties  than default

    it means that ciq has in memory all settings and then user try to change settings there is merging and delete unused

    I prepare different scopes of settings for devices to save memory  but  you can see it is waste of time if user can't change settings and it default when user setups app (nobody change settings everyday.)

Children
No Data
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries