-XX:MallocLimit is very handy to analyze runaway allocation scenarios that lead to silent OOM kills. But we silence this option if the limit break happens inside error reporting. That makes sense, since we want uninterrupted hs-err files even if the hs-err file was the result of a malloc limit break.

However, it would still be useful to have at least a warning here, for the special case that we want to catch OOM kills that happen inside - as a result of - error reporting (see JDK-8275677)