micropython.mem_info() source code

[qingvsyu]

Rewrite the code so that it returns a dictionary, not a string.

[shariltumin]

The micropython.mem_info() is not intended for scriptable usage. It returns None. The output is written directly to the REPL. What you want is esp32.idf_heap_info().

>>> import esp32
>>> hx = esp32.idf_heap_info(esp32.HEAP_EXEC)
>>> hd = esp32.idf_heap_info(esp32.HEAP_DATA)
>>> hx
[(10784, 10344, 10240, 10312), (15072, 14656, 14336, 14656), (113840, 112968, 110592, 112968)]
>>> hd
[(240, 4, 0, 4), (7288, 56, 48, 28), (15072, 14656, 14336, 14656), (16648, 4552, 4096, 4460), (86272, 11664, 11264, 11664), (113840, 112968, 110592, 112968)]
>>> 

You can ask any AI for an explanation of these numbers.

[Josverl]

Not only quantum has the Observer effect,

returning a dict ( or anything for that matter) would effect the memory state so while desirable on one hand, if implemented it would be a poisoned pill in reality.

A while ago i created a memory tracer as part of micropython-magic that observes this from the host, so "out of process" , but not quite memray
still quite insightful.
I think that since then the meminfo() output has added some information - but that should be not to hard to add.
( today I would also push those meminfo() classess into a sqlite database - but have left that exercise to the reader)