Thanks Peter, for reporting this.
We have fixed the problem for the next release.