Yup, that's the bug that was fixed in 1.01. Should no longer happen since the update, so making sure the page is fully refreshed (if playing in browser) or getting a fresh download (for stand-alone versions) should fix it.
