Deeper testing of
JDK-8241139 shows that GCLockerWithShenandoah.java reliably fails in release, and always with aggressive heuristics. Investigation shows that application manages to outpace the GC every time, and then fail with OOMe too early. We should consider keep pacing enabled even in aggressive mode. This is the day 1 issue with pacing implementation.