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
  • in reply to flowstate

    For example, I have an app that doesn’t load resources, so the number of settings strings don’t affect the amount of memory used at runtime. I had an opportunity to try to save memory by moving some fairly large fixed data into a JSON resource. But as soon as I call loadResource, the whole resource table is loaded into memory permanently, which includes memory for the app settings string entries.

    My app actually uses *more* memory after moving data into a JSON resource.

Comment
  • in reply to flowstate

    For example, I have an app that doesn’t load resources, so the number of settings strings don’t affect the amount of memory used at runtime. I had an opportunity to try to save memory by moving some fairly large fixed data into a JSON resource. But as soon as I call loadResource, the whole resource table is loaded into memory permanently, which includes memory for the app settings string entries.

    My app actually uses *more* memory after moving data into a JSON resource.

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