mimalloc allocate before initialization

[keden-greg]

Hi everyone, how are you?

I just downloaded and build mimalloc, and when I overrided the global new operator with mi_malloc it's giving me issues, I have some static std::list that's allocating memory before mimalloc could initialize, I'm I doing something wrong?

Assert is here: internal.h - _mi_ptr_page (528): mi_assert_internal(p==NULL || mi_is_in_heap_region(p)); for what I saw p is nullptr.

Thanks!

PS: The issue doesn't trigger in Release build.

Target:
Version: 3.0.1
OS: Windows 11
Platform: Win32 (x32)
LIB: mimalloc-static.lib (Debug)

[daanx]

I tried to repro but could not -- can you:

• can you send the stack trace up to the assertion failure? (btw. it might be the assertion is wrong)
• try with the latest dev3 branch if it still occurs?
• does it occur in x64 as well?
• maybe send me a minimal repro case if it is still failing in dev3

Thanks!

[keden-greg]

With latest dev issue don't happen,

Yes, it does happen for x64 as well.

What I do notice, it's that in latest dev there isn't a mimalloc-static-lib but a mimalloc-lib in the vcproj, and I'm using that one, I didn't see that option in v3.0.1, maybe I had to change someflag to enable non-static lib?

I will try with dev3.

[daanx]

Thanks! I mean the latest dev3 (which will be v3.0.2). I guess the error is for v3 only as that assertion is only in v3. Recently, the naming on windows changed to be consistent across platforms, so the static lib is now mimalloc.lib. (and the static export library for mimalloc.dll is mimalloc-dll.lib).

[keden-greg]

Update: (I always try x32 and x64 debug and release)

Tried with latest dev3 #define MI_MALLOC_VERSION 302 everything works fine.

I don't know if it was a bug, or what. I will use latest dev3 until new release is out, thanks!

PS: Is there any ETA for next update? Thanks for the good work! ✌

[daanx]

Ah, good to hear -- there were some important bug fixes so that may well have been it. I hope to update this week to v3.0.2-beta :-)