Can someone please explain/point to how the Inspect Memory tool within the Inspect function works?
I assume that it tries to figure out some kind of worst/average/some stat heap use for when the program runs. I am trying to “prune” RAM use for a program as it seems like the stack is being blown when both WiFi and BT stacks are enabled for a rather simple BT + WiFi application.
A special note and something that seems like it may be a bug is that the overview RAM+flash use and the paged breakdown do not match. The flash use is somewhat close between the two “views”, but the RAM use is much different. Why is this?
Cheers