ooo this could be a webgl context bug, we are working on fixing this @keit