For all I know, this is just an unstable Chrome Linux problem that will be sorted out shortly. I may dig into this a bit more and possibly submit a bug …