Found the source of the problem--it's fixed in v2012.4.152 which will be posted later today.