kill_and_get_minidump writes a stack-only (MiniDumpNormal) minidump on Windows. Setting the MINIDUMP_FULL_MEMORY environment variable makes the Windows write_minidump path request MiniDumpWithFullMemory instead, so heap objects (e.g. the thread that owns a lock a hung process is stuck on) can be inspected. These dumps are large, so it is opt-in only. Windows-only: on Linux/macOS kill_and_get_minidump sends SIGABRT and the dump is written in-process by Breakpad, which mozcrash does not control. Differential Revision: https://phabricator.services.mozilla.com/D310266