We are not able to re-create this problem. Please file a new bug if this happens again with the latest build.