-
Notifications
You must be signed in to change notification settings - Fork 888
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mi_free_size: pointer might not point to a valid heap region #979
Comments
It looks like std::string doesn't use the mimalloc allocator when creating string, but uses mi_free_size to release memory.
|
Is the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error:
OS: Windows 11 Pro x64
#include <mimalloc-new-delete.h> defined in main.cpp.
MyDLL is my library that I compile and use mimalloc in it. I inject MyDLL into target software that does NOT use mimalloc and for which I have NO source code.
After many initializations and releasing std::string in the code of my injected MyDLL library in the target software, this error occurs.
The error occurs when calling the delete operator in std::basic_string.
What could be the problem?
mimalloc v2.0.1
Generated solution for VS C++
mimalloc-static buiit with default parameters for Debug configuration, the only thing added is the parameter:
MyDLL compiled with MSVC:
C++ params:
Linked params:
Stacktrace:
The text was updated successfully, but these errors were encountered: