mimalloc icon indicating copy to clipboard operation
mimalloc copied to clipboard

mimalloc is a compact general purpose allocator with excellent performance.

Results 266 mimalloc issues
Sort by recently updated
recently updated
newest added

Tag 100 is assigned to "IOAccelerator" (the GPU driver stack on Apple silicon), which makes for confusing output when debugging. To avoid conflicts, use a tag in the reserved application-specific...

According to the docs for static override we should do ``` > gcc -o myprogram mimalloc.o myfile1.c ... ``` I am using mimalloc from vcpkg. But the `mimalloc.o` file is...

``` $ uname -srvmpio CYGWIN_NT-10.0-22000 3.5.3-1.x86_64 2024-04-03 17:25 UTC x86_64 unknown unknown Cygwin $ cd /tmp $ git clone https://github.com/microsoft/mimalloc.git $ cd mimalloc $ cmake -DMI_BUILD_STATIC:BOOL=OFF -DMI_BUILD_OBJECT:BOOL=OFF -DMI_INSTALL_TOPLEVEL:BOOL=ON . $...

It could be nice if we could: a) (read-only) access thread local stats b) (read-only) access _mi_stats_main getting stats via mi_heap_visit_blocks is just too expensive cpu-wise.

### Environment macOS 10.13, Xcode AppleClang 10.0.0, -std=c++17 -fno-exceptions -stdlib=libc++ macOS 12, Xcode AppleClang 13.1.6, -std=c++17 -fno-exceptions -stdlib=libc++ mimalloc v2.1.2 ### Details After all macro expansions, `mi_posix_memalign` is declared like...

Hi, I would like to debug memory allocations at runtime. Is there some kind of callback we can provide to instrumentalize our code ? Something like: ```cpp // Starting from...

windows - x86 heap = mi_heap_new() Error prone code in multithreading: address = mi_heap_malloc(heap, 666) .................................. mi_free(address) Code for safe operation without errors: EnterCriticalSection() address = mi_heap_malloc(heap, 666) LeaveCriticalSection() .....................................

Hello Daan, The project I am [working on](https://github.com/dragonflydb/dragonfly) uses mimalloc underneath. A user reported the following problem: Dragonfly reports 80GiB used memory (tracked by aggregating `mi_usable_size`) but mi_malloc stats show...

``` C:\Users\AffectedArc07\Documents\_tmp\mimalloc\bin>minject dd.exe error: use 'minject' for rewriting 32-bit PE images. ``` Should be `error: use 'minject32' for rewriting 32-bit PE images.`

We have the problem that minject.exe crashes sporadically during the build in our build environment (building with jekins, running a service in the background). The crash occurs in about 30%...