JDK-8194232 tried to fix a similar case to JDK-8292083, but still got it wrong for some cases. As JDK-8292083 bounds the memory limit above by the host total memory, we no longer need changes from JDK-8194232. In fact that old fix amounts to confusing trace output when GET_CONTAINER_INFO returns negative values (like OS_CONTAINER_ERROR, -2) on some systems. See JDK-8299424 for such a symptom:

[0.163s][trace][os,container] Memory and Swap Limit is: 18446744073709551614
memory_and_swap_limit_in_bytes: not supported

During review it was pointed out to better fix the GET_CONTAINER_INFO macros to properly handle logging of julong types in order to avoid those confusing trace logs.