This is *probably* fixed in the latest version (1.1.6). I haven't encountered it again since I put in some safeguards.
