Update mimalloc to v2.4.4 and v3.4.4 - #169
Conversation
|
@octavonce @svix-jbrown @DouglasDwyer It would be great to get this PR merged in! |
|
v3.4.4 is already out :) |
|
Is it possible to make some solution to update mimalloc without releasing a new version of crate? Other than a fork. |
|
Would it be possible to get updated to v3.4.4? It contains one critical fix for macOS (microsoft/mimalloc#1327 (comment)) |
+1 cc @xonatius |
Bump the v2 submodule from v2.3.2 to v2.4.4 and the v3 submodule from v3.3.2 to v3.4.4. The v3 bump fixes a segmentation fault in the currently shipped v3.3.2 sources: mimalloc v3.3.0-v3.3.2 crashes under multi-threaded use (SIGSEGV in _mi_theap_default_set during thread heap init), which affects this crate since v3 is the default. Fixed upstream in v3.4.x. See microsoft/mimalloc#1287.
xonatius
changed the title
|
@octavonce @svix-jbrown @DouglasDwyer possible to get this PR merged and released? As it contains a critical memory corruption fix for macOS 🙏 |
|
mimalloc v3.4.5 (and 2.4.5) released yesterday, could this MR be updated with the newer versions before merge? |
+1 cc @xonatius |
6 participants
Bump the v2 submodule from v2.3.2 to v2.4.4 and the v3 submodule from v3.3.2 to v3.4.4.
The v3 bump fixes a segmentation fault in the currently shipped v3.3.2 sources: mimalloc v3.3.0-v3.3.2 crashes under multi-threaded use (SIGSEGV in _mi_theap_default_set during thread heap init), which affects this crate since v3 is the default. Fixed upstream in v3.4.x. See microsoft/mimalloc#1287.
Resolves #168