While checking an external for memory leaks on Windows, I found that posting
to the max window seems to allocate memory which is never freed. So I
checked this using a standard "print" object, and it behaves the same. Maybe
this is intended behavior, or maybe I'm just missing something, but I
thought I'd mention it anyway. Just in case.