Make the lazy TLS pointer to the current MessageLoop into a Leaky LazyInstance.
If a joinable thread is not joined before AtExit (e.g. if it is owned by a leaky
singleton), the AtExitManager will destroy its MessageLoop pointer while the
thread is still running. Make the pointer Leaky to prevent that from happening.
BUG=270110
R=darin, jar
Review URL: https://chromiumcodereview.appspot.com/22816018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219953 0039d316-1c4b-4281-b951-d872f2087c98
CrOS-Libchrome-Original-Commit: c65f676922a747565ccba68a69f6d61f8fe009ca
diff --git a/base/message_loop/message_loop.cc b/base/message_loop/message_loop.cc
index 4fb13c2..701594a 100644
--- a/base/message_loop/message_loop.cc
+++ b/base/message_loop/message_loop.cc
@@ -44,7 +44,7 @@
// A lazily created thread local storage for quick access to a thread's message
// loop, if one exists. This should be safe and free of static constructors.
-LazyInstance<base::ThreadLocalPointer<MessageLoop> > lazy_tls_ptr =
+LazyInstance<base::ThreadLocalPointer<MessageLoop> >::Leaky lazy_tls_ptr =
LAZY_INSTANCE_INITIALIZER;
// Logical events for Histogram profiling. Run with -message-loop-histogrammer