Thanks for the report, as @LesJ said, this has been fixed for 4.1.