02-29-2020 08:08
02-29-2020 08:08
Any insight on where/how I should look to resolve an App crash with this message:
"Terminating app: Memory fault (stack overflow?)"
The studio tool does not point me to any specific code.
So far it has happened three total times I believe.
I've rebooted the watch - waiting to see if the error recurs.
Any thoughts appreciated.
02-29-2020 11:30
02-29-2020 11:30
You could try console.logging memory stats from the System API.By doing so in various places, you may be able to find out which bit of code is using too much memory.
However, if the error message is right and you're actually experiencing a stack overflow, those memory stats may not help. Consider whether you might be making any recursive function calls, or even just very deep call stacks.
03-01-2020 23:22
03-01-2020 23:22
Very helpful - I need to be examining memory usage very closely and learn what are the biggest memory culprits
I do have a lot of SVG elements and some very large arrays - need to look to optimize
Thanks!
03-09-2020 01:37
03-09-2020 01:37
You can use an analytics tool to capture the error so you can investigate further.
Try this out https://github.com/dillpixel/fitbit-google-analytics