search

caomw / google-glog

Automatically exported from code.google.com/p/google-glog
Other
0 stars 0 forks source link

GLOG leaks some memory #104

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run an application which uses GLOG under valgrind with --leak-check=full 
--show-reachable=yes parameters

What is the expected output? What do you see instead?

In the perfect case there shouldn't be any output.

What version of the product are you using? On what operating system?

Ubuntu 11.04

Please provide any additional information below.

It would be nice if GLOG could kill all the created objects in 
ShutdownGoogleLogging. It makes easier to debug leaks in applications which use 
libglog.

Original issue reported on code.google.com by alex.bes...@gmail.com on 21 Nov 2011 at 5:51

GoogleCodeExporter commented 9 years ago 
I think this was fixed in

http://code.google.com/p/google-glog/issues/detail?id=69

Sorry, this was not released yet.

Original comment by shinichi...@gmail.com on 26 Nov 2011 at 7:14