Comment #1 on issue 6052 by brettw: occasional leak in logging::InitializeLogFileHandle http://code.google.com/p/chromium/issues/detail?id=6052
I worked for several hours on making it use a Singleton (it turned into a nontrivial refactoring). However, there is a problem. We don't know the order in which singletons will be destroyed. Some destructors of other singletons might actually use DCHECKS or other forms of logging. This would set up a bad situation. This actually comes up with other parts of logging. Since basically every part of the system uses it, if logging uses any other dependencies, you can quickly get (and we have gotten) into infinite recursion situations. I think it's best if we just somehow ignore these "leaks". -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
