OK, I could reproduce this easily, too, and spotted the culprit. The fix patch is below. I'm going to send the fix to upstream.