In BF-20042 we was a memory corruption issue correlated with tcmalloc: large alloc 3761212780863488 bytes == (nil) @. Memory requested amounts to ~3.7 petabytes. A core dump followed during cache release. It is unclear, where does such large allocation originates, but it clearly is a bug.

In order to make debugging simpler we must fail-fast when it happens, so that a core dump is produced and location of fault is easier to identify.

For the purposes of this ticket, a code change should be limited in functionality to evergreen-only invocations by the use of environment variable.