I agree this is deplorable behavior. It's just that we'd need something concrete to see if we can evince it at our end. Which would be the first step in diagnosing it.
Without more detail, I will speculate that the code in question is attempting to allocate considerable memory and the OS is not gracefully declining. If it did, you'd likely get a kernel crash but nothing worse. Maybe you can run the program in a memory-restriced mode to see if that helps? (This may be OS-specific, I'm not sure.)