I just got notice that the problem has been found - it happened when two instances wrote in a log file at the same time. This will be fixed in the next update.