Skip to content
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

LogMemoryManagerStateToFile doesn't log anything when used in a Dll #59

Open
MrWaz opened this issue Oct 3, 2018 · 0 comments
Open

Comments

@MrWaz
Copy link

MrWaz commented Oct 3, 2018

Hi and thanks for your great tools.

I'm having a rough time trying to track memory leaks for memory allocated in a dynamically loaded dll.

Trying to use the standard 'report on shutdown' facility, all objects are reported as 'unknown' with no stack trace information at all. Well I can admit it as the dll has been unloaded at this time.

I then tried the LogMemoryManagerStateToFile function inside my dll to get snapshots information and do manual comparisons. Unfortunately, the function does not report anything worthy.

FastMM State Capture:
---------------------

0K Allocated
0K Overhead
100% Efficiency

Usage Detail:

It's exactly the same behavior when trying to do the same in your Dynamically Loaded DLL demo adding a call to LogMemoryManagerStateToFile in TfDLLMain.Button1Click

I'm using full debug mode and if I add the same call in the TestApplication.exe, I get a correct report.

Hope someone here can help.

Regards
Sylvain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant