Complete

Simulator not changing setting, but keeps new settings as tmp file in TEMP folder

I am facing following behavior in the sim, any idea what can be causing this please ?

1.) Watchface starts OK in sim-> set files is created using default values from properties (Memory reports 74kB Memory peak and 380 objects peaks)
2.) Modifying settings using Connect IQ - App Settings editor in Eclipse
3.) Clicking Send Settings
4.) After some time new settings processing finishes, NO changes are reflected on watchface (Simulator reports Peak Memory 82.6kB and 569 peak objects)

In the file system TEMP directory where sim is pointed i can see new file  "temp_appsettings<multiple_random_digits>.tmp" has been created on same level as GARMIN folder, but set file has not been replaced with new data.
In rare occurrence new set file is created but has 0bytes size. Working SET file has 3.98kB

tomulli
Parents
  • Update: i did not find reason why suddenly simulator and device reports 27kB less memory peak with same code, given it is on levels i expect i am ok guessing something was wrong in my environment. However i still have problem with background when on the first run available memory is significantly higher while very low on the second one. My understanding is once background task finishes its memory is freed. Jim or Garmin guys would you have some hint where to look at please ? This is Free memory details i am getting while running background. 
    Background: 11:48 Entering onTemporalEvent
Background: FreeMem Process Entry: 20504
Background: Start: 2020-06-16T09:48:14Z
Background: End: 2020-06-16T09:48:14Z
Background: 200
Background: FreeMem Before exit: 14496

Background: 11:53 Entering onTemporalEvent
Background: FreeMem Process Entry: 9448
Background: Start: 2020-06-16T09:53:14Z
Background: End: 2020-06-16T09:53:14Z
Background: 200
Background: FreeMem Before exit: 3440

Background: 11:58 Entering onTemporalEvent
Background: FreeMem Process Entry: 20504
Background: Start: 2020-06-16T09:58:14Z
Background: End: 2020-06-16T09:58:14Z
Background: 200
Background: FreeMem Before exit: 14496

Background: 12:03 Entering onTemporalEvent
Background: FreeMem Process Entry: 9448
Background: Start: 2020-06-16T10:03:14Z
Background: End: 2020-06-16T10:03:14Z
Background: 200
Background: FreeMem Before exit: 3440
    1. run - as expected 2. run - not expected, in fact entry available memory is lower than last exit one 3. run - as expected 4. run - not expected ..and it keeps alternate Each second run background available memory is so significantly lower i assume thats the place where things are getting messed up when loading same amount of json data as during run 1. (this test run was executed with smaller then expected json data sample )
Comment
  • Update: i did not find reason why suddenly simulator and device reports 27kB less memory peak with same code, given it is on levels i expect i am ok guessing something was wrong in my environment. However i still have problem with background when on the first run available memory is significantly higher while very low on the second one. My understanding is once background task finishes its memory is freed. Jim or Garmin guys would you have some hint where to look at please ? This is Free memory details i am getting while running background. 
    Background: 11:48 Entering onTemporalEvent
Background: FreeMem Process Entry: 20504
Background: Start: 2020-06-16T09:48:14Z
Background: End: 2020-06-16T09:48:14Z
Background: 200
Background: FreeMem Before exit: 14496

Background: 11:53 Entering onTemporalEvent
Background: FreeMem Process Entry: 9448
Background: Start: 2020-06-16T09:53:14Z
Background: End: 2020-06-16T09:53:14Z
Background: 200
Background: FreeMem Before exit: 3440

Background: 11:58 Entering onTemporalEvent
Background: FreeMem Process Entry: 20504
Background: Start: 2020-06-16T09:58:14Z
Background: End: 2020-06-16T09:58:14Z
Background: 200
Background: FreeMem Before exit: 14496

Background: 12:03 Entering onTemporalEvent
Background: FreeMem Process Entry: 9448
Background: Start: 2020-06-16T10:03:14Z
Background: End: 2020-06-16T10:03:14Z
Background: 200
Background: FreeMem Before exit: 3440
    1. run - as expected 2. run - not expected, in fact entry available memory is lower than last exit one 3. run - as expected 4. run - not expected ..and it keeps alternate Each second run background available memory is so significantly lower i assume thats the place where things are getting messed up when loading same amount of json data as during run 1. (this test run was executed with smaller then expected json data sample )
Children
No Data
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries