diff options
| author | evan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-02 22:58:10 +0000 |
|---|---|---|
| committer | evan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-02 22:58:10 +0000 |
| commit | 42009f379758c9ebfb7e8e97f0159e2f61a66445 (patch) | |
| tree | 9f8cc0d2104ca11ed37bf8d3eec5bfe4913c4749 /webkit | |
| parent | 394f2382df70ac8e8f5536df083cdd87f79aaee6 (diff) | |
| download | chromium_src-42009f379758c9ebfb7e8e97f0159e2f61a66445.zip chromium_src-42009f379758c9ebfb7e8e97f0159e2f61a66445.tar.gz chromium_src-42009f379758c9ebfb7e8e97f0159e2f61a66445.tar.bz2 | |
startup: move sandbox initialization together
The initialization call was happening on one place on Windows, then later on OS X.
This moves Windows down alongside OS X.
The comment above this code, dating back to 2008, says that we must initialize
the sandbox before the crash handler. But this code as it currently works
runs way after we initialize breakpad (we do breakpad in WinMain, which
then loads this code from chrome.dll and runs it) and there is no breakpad
code in between its old location and its new one.
Review URL: http://codereview.chromium.org/5439003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68093 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit')
0 files changed, 0 insertions, 0 deletions