This was due to a method being called in scalar context, which returned incorrect detail Reported by Aaron C. de Bruyn