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
  • over 1 year ago in reply to flocsy🤠

    You can see in the memory usage I posted that the app Data section went from 4K to 9K.  Yikes!

  • over 1 year ago

    1. what are your build's parameters? -O and -r at least (I used release and -O2z)

    2. do you see a difference in the Code/Data (any other???) size when you look in the Memory View? Or the difference is only in the Memory Usage/Peak Memory?

    It would be probably useful if you could find some stripped down version of your code that is possible to publish and can reproduce the problem (maybe not the whole big increase but even 0.1k increase shouldn't be there)

    BTW I just double checked my app on fenix3 in 4.1.7 uses 13.9kB and in 4.2.1 uses 14.0 kB ("Memory Usage") so no I can reproduce the problem as well. All the other numbers are identical. I can imagine that because in my case the difference is around 0.1kB it might have been so small that the last time I checked I didn't notice it.

  • over 1 year ago in reply to flocsy🤠

    I'm in direct contact with them via email.  This is a showstopper since it is breaks the ability to support older devices.  I sent them the attached memory footprints that show the rather drastic increase in memory footprint.

  • over 1 year ago

    The f6 has a max of 28k for a glance while the f7, v2 and 965 have a max of 60k.  So twice as much.

     Sounds to me you were close to the edge of 28k with 4.1.7 and now over the edge with 4.2.1.  Whatever the change was for, sounds like it's not in the FW yet.

  • over 1 year ago in reply to pstoppani

    Aware? Are they working to fix it? Or it's like the many "Acknowledged" bug reports?
    reported similar problem