@MurraySilber nope, this is 2010. The problem has been documented since 2008. I saw it happen on an early MBP once.