Epsilon exposes no metrics about memory usage of any kind. This is a deliberate design choice upstream for simplicity, but power users may want more visibility about it. A possible source of inspiration would be the mem menu on a TI-83.
Things that could be exposed in this app:
General memory usage (current and max RAM usage for both heap and stack, Flash section sizes)
Poincare usage (dedicated heaps, list of defined symbols/functions that can be erased...)
Python memory usage (Ion::Storage)
Note that since apps are essentially context-switched for memory one cannot for example audit memory usage on-the-fly in an app with this approach.
Is there already a branch for this feature?
Do you need someone working on it?
I can try to work on it if you give me some hints on how to start (i.e. template app to start from, where to read data and so on...)
What I want to see in the next version of Omega
Epsilon exposes no metrics about memory usage of any kind. This is a deliberate design choice upstream for simplicity, but power users may want more visibility about it. A possible source of inspiration would be the mem menu on a TI-83.
Things that could be exposed in this app:
Ion::Storage
)Note that since apps are essentially context-switched for memory one cannot for example audit memory usage on-the-fly in an app with this approach.