Thanks for the thorough report @wldh. We are investigating this, and will try to get a fix out in the next minor update!