IndexedDB: Fixed threading bugs with use of AtomicStrings.

Source/modules/InitModules.cpp

 // Copyright (c) 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "config.h"
 #include "InitModules.h"
 
 #include "bindings/modules/v8/ModuleBindingsInitializer.h"
 #include "core/EventTypeNames.h"
 #include "core/dom/Document.h"
 #include "modules/EventModulesFactory.h"
 #include "modules/EventModulesNames.h"
 #include "modules/EventTargetModulesNames.h"
+#include "modules/IndexedDBNames.h"
 
 namespace blink {
 
+void ModulesInitializer::init()
+{
+    if (m_isInited)

[abarth-chromium, 2014/08/12 19:51:12]

Can we ASSERT(!m_isInited) ?

+        return;
+
+    IndexedDBNames::init();
+
+    CoreInitializer::init();
+}
+
 void ModulesInitializer::initEventNames()
 {
-    EventNames::init();
+    CoreInitializer::initEventNames();

[abarth-chromium, 2014/08/12 19:51:12]

Instead, we should make an orderly init process.  That means
ModulesInitializer::init should call void ModulesInitializer::initEventNames,
not the reverse.

     EventNames::initModules();
 }
 
 void ModulesInitializer::initEventTargetNames()
 {
-    EventTargetNames::init();
+    CoreInitializer::initEventTargetNames();
     EventTargetNames::initModules();
 }
 
 void ModulesInitializer::registerEventFactory()
 {
     CoreInitializer::registerEventFactory();
     Document::registerEventFactory(EventModulesFactory::create());
 }
 
 void ModulesInitializer::initBindings()
 {
+    CoreInitializer::initBindings();
     ModuleBindingsInitializer::init();
 }
 
 } // namespace blink