Out of memory while appending to array!!!!

Hmm. Well, charCodeAt changing to cjarCodeAt looks like a memory corruption error, and it might explain why memory is getting lost.

To be honest the trace is only useful for bigger programs when you run a graphical diff to compare 'before' and 'after'.

Which board were you running this on? If possible, can you make clean and compile a version of the firmware without RELEASE=1, and if possible with DEBUG=1 on the command-line. You might have to remove USE_FILESYSTEM, USE_GRAPHICS and USE_NET from the Makefile to make room for the debug info, but it looks like you don't use them anyway.

It should compile in some assertions that may catch what the problem is. It's odd though, because I haven't noticed an error like that in 6 months or more.