We have been able to reproduce this issue and have applied a fix. The next version will address this.