I successfully downgraded to 1.5.19, but I just wanted to comment that this doesn't actually solve the problem with 1.5.20. Now that I know that a bug report has been made, I look forward to seeing...