Good Afternoon,
I am using the monitor-edge firmware on a Monitor One. I have added a few basic additional functions into the firmware. Now, I get a 13 red flash/SOS/13 red flash crash. From the vitals in the Particle Console it looks like the Memory Usage is constantly 87%. How much Memory Usage should the Monitor-Edge code on GitHub actually use? I don't see a 100% memory usage so why would it be crashing?
The memory usage reported by device vitals is heap usage. SOS+13 is stack overflow, which is different. That's caused by declaring too large of an array variable on the stack, declaring a class instance on the stack that has large class member data, or excessive recursion.
Is it safe to assume the monitor-edge on Github is safe from stack overflow issues? I am writing some custom code built on top of the monitor-edge on a MonitorOne and my code is quite simple/straightforward. Not very complex, but possibly not issue free as well. This would help me potentially isolate the monitor-edge code from the rest of the application.
