fw4.50 causes system crash on my Tabata app

When the app exits in the sim, the blue triangle is normal. It didn't exit the sim before, but the screen just went blank. I forget exactly when the triangle was added, but I'm thinking 2.3.0

I've tried building the app for latest CIQ for fenix 5 with the same issue. Can anyone give me some pointers on how to proceed?

On the note of the system crash, does an ERR_LOG.txt get generated? If so, would you post it here?

When the app exits in the sim, the blue triangle is normal. It didn't exit the sim before, but the screen just went blank. I forget exactly when the triangle was added, but I'm thinking 2.3.0

Thanks, tried running some of the samples and they behaved the same way. Seems like a fw bug since haven't done any code changes for a looong time.

On the note of the system crash, does an ERR_LOG.txt get generated? If so, would you post it here?

Yes,

2413 (fenix 3 HR) SW ver: 450
Build Type: RELEASE
ESN: 3923443625
Battery Voltage: 3.792000V
11/07/17 19:55:27
BF
PC: 0x0005e934
LR: 0x0011bffb
SP: 0x20022e90
CFSR: 0x00008200
Return Address (LR): 0x0016486b:Call Stack - PSP at 0x20022e70:
0x0011bffb
0x0011bffb
0x0011bffb
0x0011bffb
0x00007305
0x0012f8cb
0x000d4685
0x0008a16d
0x0008a16d
0x00007305
0x0008a9d9
0x0008a9d9
0x001622ef
0x00162b81
0x0005e1bd
0x001f97ef
0x0000c961
0x00092b1d
0x0000c961
0x00092b1d
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x0000af25
page addr = 0x0012e89d
page addr = 0x000b9a01
Uptime: 60842


How tight on memory are you? In the newer sims, the peak is shown in the "view memory" selection in the Sim's file menu.

Memory is really tight on the f3/f3hr. If you are recording a .fit, just that grabs about 4k out of the app's 64k max.

The same is happening on all my apps and they only use 44-48Kb.

I am linking the forum topics regarding this issue in the FAQ session of my website and I am suggesting the users to report the problem here.

geniuswrist We'd prefer it if you could collect information about a bug and post it to the Bug Reports forum (https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports) for us to investigate. The concern is that if we get several of your app users posting their issues to a thread, they may dilute the discussion with lots of unrelated topics, and the bug report could get lost in the noise.

Your users are free to report bugs to the Bug Reports forum, too, but they would be under the same standards we lay out in the reporting rules as you would be. Unless they have crash logs or something that conclusively indicates the bug is a Connect IQ bug (like a device crash log), we tend direct people back to the app developer as a first point of contact.

Hopefully that sounds reasonable. :) I don't want to dissuade anyone from getting involved in the discussions here, but we need concise, salient information when it comes to bug reports.

Oh, and I'll grab the error log from Efflon and get that reported.