This problem originated in our efforts to resolve a performance issue described by an [earlier forum post from Jinho Jung][1]. I think the problem has now been resolved by [check-in 1f6796044008e6f3][2], though testing is still on-going. [1]: /forumpost/a5fc33cf9d8f4ff5 [2]: src:/info/1f6796044008e6f3