Some memory fences (MemBar nodes) are apparently left behind after a non-escaping object is scalarized. The report is here (look for "close but not cigar"):

http://mail.openjdk.java.net/pipermail/hotspot-dev/2015-February/017194.html

Perhaps the memory barriers inserted into constructor calls by Parse::do_exits should be gated on whether the object has escaped or not.