-
Notifications
You must be signed in to change notification settings - Fork 26
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
Memory leak reported but without a stack trace #25
Comments
I changed the ini file to log using unicode instead of ascii and to write the log to a file rather than the debugger and got:
I'm not clear why that should have worked given that there don't appear to be any unicode chars in the stack trace. |
Bump ... |
Bump again ... anyone home |
I'm sure this is a bug (not reporting the call stack). Please could someone take a look |
@mattdurak: Have you seen this ticket? |
@mattdurak, @dcristoloveanu: Can you check this @perdrix52 ticket? |
VLD is reporting a new memory leak in my application, but it's not printing a stack trace:
Is there anything I can to do the get a stack trace for this block, or find out where it was allocated without one?
Thanks, David
The text was updated successfully, but these errors were encountered: