Before the changes for 6888336 (G1: avoid explicitly marking and pushing objects in survivor spaces) concurrent marking needed to be notified when the heap was expanded during a marking cycle in order to visit any of the newly-committed regions.

After the changes for 6888336 this should not be needed any more. Any new regions that are created during marking (either to-space regions or humongous regions) will have their NTAMS pointing to bottom so all objects in them will be implicitly live and not needed to be visited by the concurrent marking threads.

So, it should be sufficient to checkpoint the heap bounds at the end of the initial-mark pause and not needing to update them as future expansions take place.