Make LocalStorage persistent

webkit/api/src/WebKit.cpp

 /*
  * Copyright (C) 2009 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 20 matching lines @@
 #include "config.h"
 #include "WebKit.h"
 
 #include "WebMediaPlayerClientImpl.h"
 #include "WebString.h"
 
 #include "AtomicString.h"
 #include "DOMTimer.h"
 #include "FrameLoader.h"
 #include "Page.h"
+#include "TextEncoding.h"
 #include "V8Binding.h"
 #include "V8Proxy.h"
 #include "WorkerContextExecutionProxy.h"
 #include <wtf/Assertions.h>
 #include <wtf/Threading.h>
 
 namespace WebKit {
 
 static WebKitClient* s_webKitClient = 0;
 static bool s_layoutTestMode = false;
 static bool s_databasesEnabled = false;
 
 void initialize(WebKitClient* webKitClient)
 {
     ASSERT(webKitClient);
     ASSERT(!s_webKitClient);
     s_webKitClient = webKitClient;
 
     WTF::initializeThreading();
     WebCore::AtomicString::init();
 
     // Chromium sets the minimum interval timeout to 4ms, overriding the
     // default of 10ms.  We'd like to go lower, however there are poorly
     // coded websites out there which do create CPU-spinning loops.  Using
     // 4ms prevents the CPU from spinning too busily and provides a balance
     // between CPU spinning and the smallest possible interval timer.
     WebCore::DOMTimer::setMinTimerInterval(0.004);
+
+    // There are some code paths (for example, running WebKit in the browser
+    // process and calling into LocalStorage before anything else) where the
+    // UTF8 string encoding tables are used on a background thread before
+    // they're set up.  This is a problem because their set up routines assert
+    // they're running on the main WebKitThread.  It might be possible to make
+    // the initialization thread-safe, but given that so many code paths use
+    // this, initializing this lazily probably doesn't buy us much.
+    WebCore::UTF8Encoding();
 }
 
 void shutdown()
 {
     s_webKitClient = 0;
 }
 
 WebKitClient* webKitClient()
 {
     return s_webKitClient;
@@ skipping 63 matching lines @@
 {
     return s_databasesEnabled;
 }
 
 void enableV8SingleThreadMode()
 {
     WebCore::enableStringImplCache();
 }
 
 } // namespace WebKit