[Solved] Best practices for debugging memory corruption and free() woes?

Probably due to time and effort priorities and the need to fix what you should not be using.

I'd rather other things were addressed including getting the Tutorials that use the String Class out of the Learning section (they teach BAD HABITS) and replace with C string array examples.

dc42:
Best advice is never to call free() in embedded systems running on microcontrollers, and either never call malloc() either, or call it only in the initialization phase. Aside from any bugs there may be in malloc/free, using dynamic memory can result in memory fragmentation, which eventually results in running out of RAM.

+1 with extreme agreement!

Trying to make like MCU code should be the same as PC code is really hardware ignorant.
It's possible for small things but it is very bad practice that hurts the user in the not-so long run.