The problem has been found and will be fixed in the 1.5.0.1 maintenance release (that should be out real soon now).