Watch app stops randomly after running for 1 hour

ArtaudAntonin / Jiri Richter over 6 years ago

Hi,

I have a sleep tracking app that needs to run for about 8 hours straight. This was working for me most of the time, but recently I've got a few reports from users that after about an hour, the app on the watch exits by itself.
It happened on Vivoactive 3 and Fenix 5.

Does anybody have any idea why this might happen? Is there anything in the platform that would kill running apps if they run for too long, or consume too much battery etc.? Any hints on where could I start the investigation?

Thanks a lot
Jiri

ArtaudAntonin / Jiri Richter over 6 years ago

Update: I've just got a crash report from one user. Should this maybe be moved into the bug reports section?

2697 (fenix 5) SW ver: 1000
Build Type: RELEASE
Commit:bef5fea663aeec52575bd5b5b91e2d15afc92b7d
ESN: 3962006839
10/07/18 02:17:42
RTL
errnum: 0x00a
r0: 0x2005bd40
r1: 0x00000063
r2: 0x0000007e
r3: 0x0000007f
r4: 0x000a4a49
Stack frame PC, SP: 0x000cceb9, 0x2005b948
Call Stack - SP at 0x2005b948:
    0x000704cf
    0x000a4a49
    0x0008cba5
    0x000a4a49
    0x000a4a49
    0x0008d82d
    0x000a551d
    0x0001011d
    0x0000b475
    0x00070675
    0x0008d82d
    0x0008d82d
    0x0008d6bd
    0x00020075
    0x000a4c89
    0x00027983
    0x0002621b
    0x0001fdeb
    0x0008d82d
    0x0008d6bd
    0x0008d6db
    0x0008e9a5
    0x0004f255
    0x0004f0ad
    0x0005d523
    0x00011985
    0x0005d571
    0x0005d57d
    0x0008ea8b
    0x000e5b47
    0x0008b80d
    0x00000000
Uptime: 4880819

Coleman.Apps over 6 years ago

Jiri,

I've got this reported and I'm having the device team look at the error log to figure out what is causing the crash.

Thanks,
-Coleman

ArtaudAntonin / Jiri Richter over 6 years ago

Thank you very much Coleman!
Just for clarification - by "I've got this reported", do you mean that it was reported by someone else as well? Do you by any means have a forum link if it was on a forum?

Thanks
Jiri

Coleman.Apps over 6 years ago

ArtaudAntonin,

That means I've reported to the fenix 5 device team specifically and created a ticket for them to work out the bug. I have linked the ticket to this forum link so they/I can refer to it for additional communication and info as needed.

Thanks!
-Coleman

ArtaudAntonin / Jiri Richter over 6 years ago

Coleman.ConnectIQ thanks a lot!
I've got another very similar device crash, this time from Vivoactive 3.

We're trying to debug this issue in our Github tracker, so far it seems to us as if there was a memory leak somewhere, either in our app or in the VM itself.
The situation is that our app should be running for about 8 hours straight, but after 1 hour it stops. I've been doing extensive logging in my app (multiple times per second - but most users never had the logfile actually created, so there were no filesystem write operations).
I removed the logging, and the watch started crashing after a longer period - about 4-5 hours.

2700 (vívoactive 3) SW ver: 540
Build Type: RELEASE
Commit:38eeb66ab91c4dbbb90282ab9eea0f28012192aa
ESN: 3961220313
10/17/18 03:38:50
RTL
errnum: 0x800a
r0: 0x00000090
r1: 0x0000007e
r2: 0x0000007f
r3: 0x0016bf53
r4: 0x00000000
r5: 0x00000000
r6: 0x00000000
r7: 0x00000000
r8: 0x00000000
r9: 0x00000000
r10: 0x00000000
r11: 0x00000000
r12: 0x00000000
r13: 0x00000000
r14: 0x00000000
r15: 0x00000000
r16: 0x00000000
r17: 0x00000000
r18: 0x00000000
r19: 0x00000000
r20: 0x00000000
r21: 0x00000000
r22: 0x00000000
r23: 0x00000000
Stack frame PC, SP: 0x00197fcd, 0x1fff2398
Call Stack - SP at 0x1fff2398:
    0x00198571
    0x0016bf53
    0x001480d7
    0x0002729f
    0x0013076b
    0x0016bf53
    0x00148129
    0x0016bf53
    0x0016bf53
    0x00148d4b
    0x0016c867
    0x00148a0b
    0x0000f07d
    0x044ec9e1
    0x00148d4b
    0x00148d4b
    0x00025e43
    0x0016c155
    0x0003b8a1
    0x0003a1e1
    0x00025b03
    0x00148d4b
    0x00148d4b
    0x00148bad
    0x00148bad
    0x00149d83
    0x000ff243
    0x00148bad
    0x0010c857
    0x00011985
    0x0010c885
    0x0010c891
Uptime: 21545082

jim_m_58 over 6 years ago

Have you tried running for a long period in the sim with one of the targets that crashed? Keep an eye on the "View Memory" window, and maybe you'll see something like peak memory or objects increasing. It's actually kind of hard for a CIQ app to crash a watch, and what you see could provide some hints.

When you said that it runs longer without the logging, that could be because memory usage changed.

ArtaudAntonin / Jiri Richter over 6 years ago

Thanks Jim for the tip, I have run the tests for several hours with no memory/objects increase observed.
So unfortunately this is not the case. I also have to take back the previous claim about running longer with logging disabled, it did not prove to be true.

So still no idea what might be causing the crashes...

ArtaudAntonin / Jiri Richter over 6 years ago

Just reproduced this on old Vivoactive

1907 (vívoactive) SW ver: 450
Build Type: RELEASE
ESN: 3913321567
Battery Voltage: 4.116000V
11/13/18 23:53:56
RTL
errnum: 0x00A
r0: 0x200128B8
r1: 0x00000085
r2: 0x0000007E
r3: 0x0000007F
Return Address (LR): 0x000D96C9:Call Stack - PSP at 0x20012668:
0x0001FC25
0x000D96C9
0x000A5CD5
0x00020CD3
0x000C48C5
0x000B73D1
0x000C48C5
0x000C48C5
0x000C520B
0x000941DF
0x000B7E1F
0x00091679
0x000B63DB
0x000916BD
0x000C4B35
0x00020C57
0x00020E27
0x000200FF
0x0002161B
0x0008FE09
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x00059F8D
page addr = 0x0003CF29
Uptime: 24728914

SirLanceLot over 4 years ago in reply to ArtaudAntonin / Jiri Richter

Hi ArtaudAntonin!
I’ve been having the same sort of problem in my own app. I get a mysterious crash on my device at seemingly random times. The error log looks a lot like these. I use a vivoactive 3. Did you ever get this problem figured out?

Thanks!

Lance