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

  • Yes, you are right some are good but some unfortunately not.

    I've decide to write my own WF because I couldn't find anything that in 100% met my requirements (and of course I like to write software and to be honest it was a good lesson :)).

    The biggest problem is with 240x240 devices, 94kB is a little to small  should be 100 and in my opinion, the size of the screen does not matter in the case of memory, except for buffered bitmaps, but this can be managed by developer (most of the memory is practically occupied by code, data, settings and resources that are practically independent of the device).

    Using devices settings probably doesn't solve problem with the peak.

    And as usually, any more work and I'll protect app from the problem...

Comment

  • Yes, you are right some are good but some unfortunately not.

    I've decide to write my own WF because I couldn't find anything that in 100% met my requirements (and of course I like to write software and to be honest it was a good lesson :)).

    The biggest problem is with 240x240 devices, 94kB is a little to small  should be 100 and in my opinion, the size of the screen does not matter in the case of memory, except for buffered bitmaps, but this can be managed by developer (most of the memory is practically occupied by code, data, settings and resources that are practically independent of the device).

    Using devices settings probably doesn't solve problem with the peak.

    And as usually, any more work and I'll protect app from the problem...

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