- Wed Feb 24, 2016 3:52 pm
#41825
The node.heap() function shows the total amount of available memory on the heap. If the heap is fairly fragmented there might be a lot of small free pieces that sum up to a big number. It seems that you have enough headroom to further consume heap. But once the firmware tries to allocate a larger chunk and that doesn't fit into one of the free slots... out of memory.
- Thu Feb 25, 2016 11:39 pm
#41902
Devsaurus, this sure is a good theory. It's just so that I'm running the test right after a reboot, so I wouldn't think much allocation/deallocation causing gaps has happened.
- Sat Mar 05, 2016 3:10 pm
#42501
Look at the source for goodness sake. The table allocator uses a doubling algo, so to store the 513th entry it must allocate a new 1024* size_t vector ( and after the copy free the old 512 entry copy. Allocatin chunks that size can fail when you've only got ~8Kb left.
Please see my Developer FAQ for Q&A on nodeMCU Lua before asking a question here that's already been answered. This and the other official documentation should be your first reference for developing Lua Apps
