During review of JDK-8269908 it became obvious that MXBeans peak memory usage is updated one gc too late.
At least for g1 this behavior has been the case for forever, as apparently there is no test for that (some tier1-5 run did not find anything).

Create a test that verifies that the peak memory usage MXBean contents are updated correctly during gc.