diff options
author | joi@chromium.org <joi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-28 12:51:39 +0000 |
---|---|---|
committer | joi@chromium.org <joi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-28 12:51:39 +0000 |
commit | 042666f262a0c2ff601402e95f94fe9664a03f17 (patch) | |
tree | 508140a07a104fd3dd03b4c4c6548161de30f67f /content/public/browser/browser_shutdown.h | |
parent | 1d697f38d70b8edaca243a49f790b525c1c95a9d (diff) | |
download | chromium_src-042666f262a0c2ff601402e95f94fe9664a03f17.zip chromium_src-042666f262a0c2ff601402e95f94fe9664a03f17.tar.gz chromium_src-042666f262a0c2ff601402e95f94fe9664a03f17.tar.bz2 |
Have content/ create and destroy its own threads.
Change embedding API and embedders to allow for this.
Push inheritance of base::Thread down to content::BrowserThreadImpl so
that content::BrowserThread is just a namespace for API functions.
This change temporarily disables chrome_frame_net_tests as agreed by the CF lead, see bug 105435.
TBR=ben@chromium.org (IWYU change only)
BUG=98716,104578,105435
Review URL: http://codereview.chromium.org/8477004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111695 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/public/browser/browser_shutdown.h')
-rw-r--r-- | content/public/browser/browser_shutdown.h | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/content/public/browser/browser_shutdown.h b/content/public/browser/browser_shutdown.h new file mode 100644 index 0000000..72a4ce0 --- /dev/null +++ b/content/public/browser/browser_shutdown.h @@ -0,0 +1,32 @@ +// Copyright (c) 2011 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. + +#ifndef CONTENT_PUBLIC_BROWSER_BROWSER_SHUTDOWN_H_ +#define CONTENT_PUBLIC_BROWSER_BROWSER_SHUTDOWN_H_ +#pragma once + +#include "content/common/content_export.h" + +namespace content { + +// This can be used for as-fast-as-possible shutdown, in cases where +// time for shutdown is limited and we just need to write out as much +// data as possible before our time runs out. +// +// This causes the shutdown sequence embodied by +// BrowserMainParts::PostMainMessageLoopRun through +// BrowserMainParts::PostDestroyThreads to occur, i.e. we pretend the +// message loop finished, all threads are stopped in sequence and +// PreStopThread/PostStopThread gets called, and at least, +// PostDestroyThreads is called. +// +// As this violates the normal order of shutdown, likely leaving the +// process in a bad state, the last thing this function does is +// terminate the process (right after calling +// BrowserMainParts::PostDestroyThreads). +CONTENT_EXPORT void ImmediateShutdownAndExitProcess(); + +} // namespace content + +#endif // CONTENT_PUBLIC_BROWSER_BROWSER_SHUTDOWN_H_ |