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

Memory leaks reported by Visual Studio's heap checker #970

Closed
jdukat opened this issue Dec 24, 2016 · 2 comments
Closed

Memory leaks reported by Visual Studio's heap checker #970

jdukat opened this issue Dec 24, 2016 · 2 comments

Comments

@jdukat
Copy link

jdukat commented Dec 24, 2016

Hi,
When heap checking is enabled as explained in this article:

I get several (~10) heap leaks caused by gtest code.
Stack traces on allocation breakpoints are quite complex and may be specific to my code, so for now just the question: is anyone else experiencing this also? Maybe a known issue?

@ynikanchyk
Copy link

Vote for "yes, it's a known issue". Take a look on #892, it has some more references. Or, just use this for actual state : https://github.com/google/googletest/issues?utf8=✓&q=is%3Aissue%20is%3Aopen%20memory%20leak .

As for me, the workaround at #757 doesn't work (crashes probably because of wrong order of statics destruction), and #892 seems to be ok (but can't see if this PR is a real reason of failed checks at https://ci.appveyor.com/project/BillyDonahue/googletest/build/83, seems it's not).

@gennadiycivil
Copy link
Contributor

Should be addressed by #1142

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

3 participants