Daan
Daan
@michaeleisel: do you mean there is crash when dynamically overriding malloc with mimalloc in XcodeProj ? Not when you create programs using mimalloc directly right? The comment by @erikolofsson is...
Yes, that is right -- still gearing up for a new release soon! There is a somewhat big change in 1.8.4 and 2.1.4. On certain workloads with large services we...
ah, strange error -- looks like the heap pointer is wrong which is very strange. Can you create a repro for testing?
What OS is this? I am guessing now that the 3rd party plugin is using a different allocator and a thing allocated with mimalloc/the other allocator is freed by the...
Hi @xhochy , lucky you with an M1 :-) Thanks @devnexen for looking into this. Unfortunately, there have been various issues on macOS and it may be related to that...
@xhochy, I just pushed an update for macOS ; can you try again with the latest `dev` ? (may not make a difference but then we know at least it...
Hmm, I wish I had an M1 to test with; It is always tricky on the mac as the loader calls `malloc` to initialize thread local state but with the...
I believe we figured out a way to make this work -- thanks so much! Really nice to see how this could be patched and merged without me having an...
Hi @xhochy -- this has taken awhile but I think I fixed the issue in the latest releases (v1.7.2, v2.0.2). The issue was two-fold; we need indeed the `tldrro_el0` register...
The mimalloc version v1.7.3 and v2.0.3 have much improved support for macOS -- perhaps this also fixes the problem on iOS?