Daan

Hi @ArsMasiuk; > It looks like mimalloc 2.0.4 (from trunk) causes a memory leak somewhere. Ah, I was changing a lot yesterday doing experiments. What commit did you use? (use...

Thanks for the report! Yikes -- I hope we can figure out what this is. The `_mi_block_nextx` just reads the next field in the linked list of delayed free nodes...

> @austenstone I'm digging further, but this change trips the UB sanitizer on my ARM Mac when landed against the dev3 branch. I see you've landed it against the dev3-cdb...

Thanks for the report. However, it is not recommended to use the `dev3-cdb` branch. I believe this issue is not present for the `dev3` branch (or `dev2` or `dev1`) (at...

Thanks! Can you still try the latest `dev3` and see if that also fixes the crash (I'm going to do a fresh release soon and it would be good to...

Apologies for the late reply -- the latest `dev3` is in a very good state and marking it "beta" is perhaps a bit too conservative as it has been running...

Interesting and thanks for porting mimalloc to QNX :-) Most special cases are often to improve performance so I would first try to find a way to make it work...

Ah, that should not happen; my suggestions were for either a regular thread local variable, or pthreads, but not the `_SLOT` variants. Is QNX defining `__mach__` or something? Can you...

Just to expand a bit on the mechanics: when overriding `malloc` it becomes available even at load time before even the C runtime is initialized. So, mimalloc is very careful...

Did you make any progress? Is there any easy way perhaps for me to access a QNX system somewhere to debug on? I think these kind of recursive threading issues...