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

André Zunido over 1 year ago
Just did a build for fenix 6 using 4.1.7 and its a whopping 10k drop in peak memory usage when compared with 4.2.1. So I guess it depends on the code?

4.1.7

https://drive.google.com/file/d/10rA9lEOv_ijw1RkT2Jqfam5drSSq88wd/view?usp=share_link

4.2.1

https://drive.google.com/file/d/1Yr_LCFoTtwvtzPoFgQ4y3el3Yh_VQoGy/view?usp=share_link

That is an hefty memory footprint increase of almost 17%.
When memory is already so limited, this is a heavy price to pay.
Regardless, I'm open to ideas regarding solving this. I already implemented all optimization tricks I could find, and dropping features would introduce a real regression for users.

Apart from the coding optimization tricks I use the following project settings in the monkey.jungle when building:
```
project.typecheck = 0
project.optimization = 2
```
Is there any automated way to further optimize?
- Cancel
- Up 0 Down
- More
- Cancel

Comment

André Zunido over 1 year ago
Just did a build for fenix 6 using 4.1.7 and its a whopping 10k drop in peak memory usage when compared with 4.2.1. So I guess it depends on the code?

4.1.7

https://drive.google.com/file/d/10rA9lEOv_ijw1RkT2Jqfam5drSSq88wd/view?usp=share_link

4.2.1

https://drive.google.com/file/d/1Yr_LCFoTtwvtzPoFgQ4y3el3Yh_VQoGy/view?usp=share_link

That is an hefty memory footprint increase of almost 17%.
When memory is already so limited, this is a heavy price to pay.
Regardless, I'm open to ideas regarding solving this. I already implemented all optimization tricks I could find, and dropping features would introduce a real regression for users.

Apart from the coding optimization tricks I use the following project settings in the monkey.jungle when building:
```
project.typecheck = 0
project.optimization = 2
```
Is there any automated way to further optimize?
- Cancel
- Up 0 Down
- More
- Cancel

Children

André Zunido over 1 year ago in reply to pstoppani

Yes I only used localized strings for the UI (I support 4 languages with ~100 strings each).

Hope Garmin can find the issue and fix it!
- Cancel
- Up 0 Down
- More
- Cancel
pstoppani over 1 year ago in reply to André Zunido

That's close to my experience. 4.2.1 is 5K bigger.

I don't think there is anything we can or should do to fix this. Garmin needs to fix it.

Does your app have a lot of localized strings? Mine does. I'm wondering if the build system is accidentally including resources for other devices. Just a guess.

Anyway, I'm hoping Garmin will have a fix shortly. They already fixed some issues I was having with complications in 4.2.1 so I think they are giving some priority to fixing 4.2.
- Cancel
- Up 0 Down
- More
- Cancel