IndexedDB: Fixed threading bugs with use of AtomicStrings.

Source/modules/InitModules.cpp

Index: Source/modules/InitModules.cpp
diff --git a/Source/modules/InitModules.cpp b/Source/modules/InitModules.cpp
index b1b14e6a5fcb33e5b9580f7c24e04550a86839ec..b17f9bb45f8a86de6bc01b0f2da33d957b6319dc 100644
--- a/Source/modules/InitModules.cpp
+++ b/Source/modules/InitModules.cpp
@@ -11,18 +11,29 @@
 #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();
 }
 
@@ -34,6 +45,7 @@ void ModulesInitializer::registerEventFactory()
 
 void ModulesInitializer::initBindings()
 {
+    CoreInitializer::initBindings();
     ModuleBindingsInitializer::init();
 }