Thanks for your reply.
Yes, sure enough. I spent a little extra time looking into it and it turned out to be caused by a directory structure that had been created containing a couple of blank directory names.
So, the actually bug is that X1 doesn't handle well the error path condition of invalid folder names.
Yes, sure enough. I spent a little extra time looking into it and it turned out to be caused by a directory structure that had been created containing a couple of blank directory names.
So, the actually bug is that X1 doesn't handle well the error path condition of invalid folder names.