Thanks, I haven't been able to reproduce it yet but have pinpointed a line of code in the sorting routine that is probably the cause. This should be fixed in the next version.