Under Review
over 1 year ago

SDK 4.2.1 breaks compatibility with fenix 6 (only in simulator?)

Both fenix 6 and fenix 6 pro now break in the simulator (worked fine in 4.1.7).

fenix 6 breaks with an out-of-memory error when pressing Enter key on the glance view. I added breakpoints to the widget entry points, but the widget is never loaded, it runs out of memory in garmin's CIQ code.

fenix 6 pro runs out of memory from the start and never enters the code (using the debugger).

Error: System Error
Details: Failed loading application

Encountered app crash.


Works fine on e.g. venu, fenix 7, fr 965, etc.
Also fenix 6 pro runs fine if I disable the glance view in the simulator.
I would prefer to not have to rollback the SDK version since it would lose support for the newer devices.

I have a fenix 6 pro device and the widget runs fine on it (with glances enabled), on the other end I received several reports of users with fenix 6 (non pro) that now cannot open the widget.

I can follow-up with more info, just contact me.

André Zunido
Parents
  • over 1 year ago

    I had problem with memory only on widget (no problem with wf, df...). The last test I did, before I have stopped playing with 4.2.1, was putting app into device with memory checking and it was good without +5kB. But of course i could see memory only after app was loaded so if the problem is when app is loaded couldn't see it.

    I think that bug in 4.2.1 is that in glance ciq load all code/data not only annotated (:glance)!

    The problem is also with settings because ciq need 2x more memory on start and when you change it (bug report about is years old). And all settings are loaded also in glance (forums.garmin.com/.../feature-request-managing-of-memory-connecting-with-settings)!

    glance after start peak +5.4kB

    glance after changing settings peak +9.9kB

    If you have settings you have leave free memory on level x2 size(incl. children) of settings.

Comment
  • over 1 year ago

    I had problem with memory only on widget (no problem with wf, df...). The last test I did, before I have stopped playing with 4.2.1, was putting app into device with memory checking and it was good without +5kB. But of course i could see memory only after app was loaded so if the problem is when app is loaded couldn't see it.

    I think that bug in 4.2.1 is that in glance ciq load all code/data not only annotated (:glance)!

    The problem is also with settings because ciq need 2x more memory on start and when you change it (bug report about is years old). And all settings are loaded also in glance (forums.garmin.com/.../feature-request-managing-of-memory-connecting-with-settings)!

    glance after start peak +5.4kB

    glance after changing settings peak +9.9kB

    If you have settings you have leave free memory on level x2 size(incl. children) of settings.

Children