It could also be #3542 from the description. And, after some hackery last night, has now got an internal bug ID against it - and hopefully enough information to pin it down.