Hi Hamish,
there was a similar error report recently - did you check that out?
Maybe there is a real bug afoot somewhere…