Comment #5 on issue 30177 by j...@chromium.org: Crash in TimeTicks::Now() http://code.google.com/p/chromium/issues/detail?id=30177
As it currently stands, the AtExit manager *MUST* be initialized from a single thread, and then, the exit callbacks must be run in a single threaded mode, and must never create additional singletons. The coding style as it appears today is not thread safe, and is vulnerable to races and crashes. I'd even suggest that it should have clear states, that preclude (via CHECK() calls) the addition of any new callbacks after we've started the execution of exit-time callbacks. I would therefore question actions which require simulated exits, without a fair amount of additional code (including some meta-code that relates to an absolute end- of-process, so that locks won't be destroyed before that point.) -- 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
