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 _psx_

    "or symbol should have constructor from string_number"

    Yeah, the inability to convert from a symbol to a number is a separate issue which isn't directly related to what I was talking about.

    I get that you don't like to have another array of symbols because it wastes memory but there's not much that can be done about that, either. I think the idea is that the dev is not supposed to know about the implementation details of Symbol, just the fact that it's a "lightweight unique identifier".

Comment
  • in reply to _psx_

    "or symbol should have constructor from string_number"

    Yeah, the inability to convert from a symbol to a number is a separate issue which isn't directly related to what I was talking about.

    I get that you don't like to have another array of symbols because it wastes memory but there's not much that can be done about that, either. I think the idea is that the dev is not supposed to know about the implementation details of Symbol, just the fact that it's a "lightweight unique identifier".

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