Crash in `mi_process_done` on M1 (when exiting)

When using mimalloc as a static library in a standalone process, `mi_process_done` calls `mi_collect`:

https://github.com/microsoft/mimalloc/blob/0560fc27c08d28d523b7f741a42deb26cd01c0c6/src/init.c#L536-L544

This causes a crash sometimes:


I suspect the cause might be related to resizing buffers originally created in a different thread, sometime earlier in the application's lifecycle? I've noticed occasional crashes in mimalloc when reallocating arrays.

In this application's case, we don't actually need to call `mi_collect(true)` since the program is an executable and it statically links mimalloc?

Incase it helps, here are stats from activity monitor. I believe the 390 GB of virtual memory is mostly due to JavaScriptCore's [Gigacage](https://phakeobj.netlify.app/posts/gigacage/)

Start in src/init.c at the mi_process_done and mi_collect calls linked in the issue, then investigate the reported standalone statically linked M1 exit path and the occasional reallocating-array crashes. Done means the reported crash is explained and no longer occurs in that scenario; the issue does not name a test to run.

Written by the indexing model from the issue text.