microsoft / microsoft/mimalloc

Any luck with memory profiling in Visual Studio

Open
#606 0 comments 7 reactions 0 assignees View on GitHub
Dominant language
C
Stars
13.4k
Forks
1.2k
Avg merge
4d 45m
Merged PRs (30d)
13

Description

I've tried the Visual Studio memory profiler with an application using mimalloc as an allocator, but the profiler cannot track the memory allocations. However, it should be possible, as there are `__declspec(allocator)` annotations in the source code. Any Ideas?

And yes, the profiler works correctly when I compile the app without mimalloc.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Visual Studio memory-profiler behavior with the application compiled with and without mimalloc. Investigate whether the __declspec(allocator) annotations in the source are recognized in the mimalloc build; done means allocations are trackable when mimalloc is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.