1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
// Copyright (c) 2009 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 "chrome/browser/in_process_webkit/webkit_context.h"
#include "chrome/browser/chrome_thread.h"
WebKitContext::WebKitContext(const FilePath& data_path, bool is_incognito)
: data_path_(data_path),
is_incognito_(is_incognito),
ALLOW_THIS_IN_INITIALIZER_LIST(
dom_storage_context_(new DOMStorageContext(this))) {
}
WebKitContext::~WebKitContext() {
// If the WebKit thread was ever spun up, delete the object there. If we're
// on the IO thread, this is safe because the WebKit thread goes away after
// the IO. If we're on the UI thread, we're safe because the UI thread kills
// the WebKit thread.
MessageLoop* webkit_loop = ChromeThread::GetMessageLoop(ChromeThread::WEBKIT);
if (webkit_loop)
webkit_loop->DeleteSoon(FROM_HERE, dom_storage_context_.release());
}
void WebKitContext::PurgeMemory() {
// DOMStorageContext::PurgeMemory() should only be called on the WebKit
// thread.
//
// Note that if there is no WebKit thread, then there's nothing in
// LocalStorage and it's OK to no-op here. Further note that in a unittest,
// there may be no threads at all, in which case MessageLoop::current() will
// also be NULL and we'll go ahead and call PurgeMemory() directly, which is
// probably what the test wants.
MessageLoop* webkit_loop = ChromeThread::GetMessageLoop(ChromeThread::WEBKIT);
if (MessageLoop::current() == webkit_loop) {
dom_storage_context_->PurgeMemory();
} else if (webkit_loop) {
// Since we're not on the WebKit thread, proxy the call over to it. We
// can't post a task to call DOMStorageContext::PurgeMemory() directly
// because that class is not refcounted.
webkit_loop->PostTask(FROM_HERE,
NewRunnableMethod(this, &WebKitContext::PurgeMemory));
}
}
|
