Aplite crashes

[chaseadam]

Seems this watchface causes my Aplite to go into SOS recovery mode. Someone mentioned that if a watchface crashes a few times, then it will push the watch into this mode. I am happy to debug but am not familiar with next steps.

[stefanheule]

I'm sorry to hear that. Let's see if we can narrow the problem down. I don't have a aplite Pebble, so it might be a bit hard for me to reproduce the problem.

Do you ever observe the watchface crashing directly? Or is the only symptom that the watch enters SOS recovery mode? Does the problem happen with other watchfaces?

[chaseadam]

The only symptom is entering SOS. I may have seen this behavior once before over the last year or two (I was using the weather watchface), but cannot recall. Since switching to this watch face, SOS has occurred 3 times. Since switching back to the built in Tic Toc watchface (currently), I haven't seen an SOS screen.

[stefanheule]

Okay, I'll try to google a little and see if I can find any possible causes. Unfortunately without being able to reproduce the problem myself, I'm not sure if I can fix it :( If you learn any more information that might be useful, though, please do share it with me, and I'll try to look into it.

[chaseadam]

I am happy to perform any debugging or test any code with some guidance.

[stefanheule]

Thanks for the offer. If I have any ideas how to debug, I'll let you know. Right now I don't have any concrete ideas.

[chaseadam]

I experienced the crash yesterday and it reminded me of the couple times it occured
The crash appears to be when redrawing after receiving a notification.

[stefanheule]

Okay, that's useful to know. Let me see if I understand correctly: When you receive a notification, and you dismiss it on the watch (i.e. the watchface would show again), Obsidian crashes and puts your watch in SOS mode. Is that accurate?

[chaseadam]

The watch crashes when dismissing the notification and I watch the watch reset. I haven't actually seen it go from notification to SOS, but my understanding is that the watch will go into SOS mode if the watchface crashes 3 times.

…

On Thu, Apr 6, 2017 at 2:10 PM, Stefan Heule ***@***.***> wrote: Okay, that's useful to know. Let me see if I understand correctly: When you receive a notification, and you dismiss it on the watch (i.e. the watchface would show again), Obsidian crashes and puts your watch in SOS mode. Is that accurate? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUU57doUgV3Cm9OwRc56PArlfUgQfwnks5rtSqxgaJpZM4MzXwZ> .

[stepardo]

I experienced this problem as well on two of my aplites. An idea might be, that the watchface has a memory leak. Afaik pebble OS does not have means to free memory for watchfaces, so they need to be very careful to free memory itself. Receiving a notification and dismissing it runs through the lifecycle of the watchface. That is, if there is memory left after closing the watchface, it will most likely remain.

I did not look into the sources yet, so take my comment with a grain of salt.

I really like this watchface, and I would like to take this opportunity to thank the author for creating it and making it open source!