Device crash - ERR_LOG.txt - Fenix 3 HR - SW ver: 430 / 450

It seems that the problem is generalized, and not related to makeImageRequest. I got a review on another app:

Calendar
https://apps.garmin.com/en-US/apps/a983be66-9e7e-4a73-98b0-3466c2007dfc

"Previous version was excellent. Current version reboots when trying to change the theme (color scheme). If this gets fixed it’s a 5 star widget!"

I am also receiving reports for my apps; it started after the latest firmware update.

I was capable of making the app crash when trying to resume, save and discard activity sessions, the errors occurred in Fenix 3 and Fenix HR.
In my case, the watch rebooted, and nothing registered in the ERR_LOG.txt file.

The part of the code that executes this function is stable for a long time. In fact, the apps were so stable that I do not remember the last time I received a crash report

The problem is not repeatable, I tried several times and 1 out of 5 times the watch freezes and reboots after saving, discarding or resuming a session, 4 out of 5 times everything works as expected.

If you need any additional help or information to work on the issue please contact me.

Cheers

This seems related to my released app crashing after latest fw 4.50. For me it seems to be related to Ui.PopView and maybe close to memory limit, could that make sense?

I don't think so; my Workout Genius app requires 44-48 Kb. It has a nice safety margin to memory limits.

Garmin Guys? There is anything you can add to this topic? I am receiving a lot of complaints, and I need to provide some answer to my users. Fenix 3 and HR users are the only ones reporting watch reboot problems during activity session saving, but they represent a significant percentage of my user base.

I have to report a bug. Lately, when I save an activity, using the app Workout Genius, https://apps.garmin.com/it-IT/apps/809e9361-a996-4c1b-a97b-c20c0ecc1501
the watch reboots and when it resumes, in the history the activity can not be consulted. It is called Non Valid and there is no data. My watch is Fenix 3 hr sapphire and it happens since I installed Firmware 4.50. Thank you

There seems to be an influx of issues coming in on the latest firmware for the F3 and F3HR. I've attached these reports to the ticket with the f3 team. Thank you all for your hard work!

-Coleman

There seems to be an influx of issues coming in on the latest firmware for the F3 and F3HR. I've attached these reports to the ticket with the f3 team. Thank you all for your hard work!

-Coleman

Thanks!

There is another kind of bug. This time watch doesn't crash during saving results, but when I synch it to have the changes made online.
Example: on workout Genius website page, I create a workout and save it. Then, on the watch, I start app and in setup options I click on Sync. Then The watch crash and reboots
I hope I've been clear

I have a similar issue. Fortunately I'm able to reproduce on my own device.

Crashes started appearing after the system update. There's one path that has not been changed for a very long time and I've been using it every day myself without any issues.
Now it causes the device to restart and the app looses all data every time.
I have no idea how to debug this.

I'm using a Fenix 3 HR.

Garmin, is there any new information regarding this problem?

I'm getting a system restart every time I hit the same path. There is no output in application log, this is the only thing in ERR_LOG.TXT:

```
2413 (fenix 3 HR) SW ver: 450
Build Type: RELEASE
ESN: 3931297329
Battery Voltage: 3.820000V
11/10/17 12:34:45
BF
PC: 0x0005e934
LR: 0x0011bffb
SP: 0x20022e90
CFSR: 0x00008200
Return Address (LR): 0x0016486b:Call Stack - PSP at 0x20022e70:
0x0011bffb
0x0011bffb
0x0011bffb
0x0011bffb
0x0000cf05
0x0012f8cb
0x000d4685
0x0008a16d
0x0008a16d
0x0000cf05
0x0008a9d9
0x0008a9d9
0x001622ef
0x00162cbb
0x0005e1bd
0x001f97ef
0x0000c961
0x00092b1d
0x000ad8f7
0x00162bd5
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x0000af25
page addr = 0x0012e89d
page addr = 0x000b9a01
Uptime: 713229
```

I'm afraid my users that have Fenix 3 watches experience the same issue.
But there is no way to even find out.

Can you provide some ETA on figuring this out? We need to let the users know what they should expect..