This looks like still the old bug of 1.59. It was a blind fix, so it's indeed possible that it only appeared to be fixed and the bug is still there. Can you send the log to Support? It seems that they have to look into it again.