Bug found and fixed. In the words of our mightly Kovid
That was an interesting bug. There was an unsafe conversion of
char->wchar_t that for some reason (probably a change in the memory
layout of 0.9.5, that caused the adjacent memory location to no longer be 0)
never caused problems before.