summaryrefslogtreecommitdiffstats
path: root/content/browser/zygote_main_linux.cc
Commit message (Collapse)AuthorAgeFilesLines
* Allow browser to startup on openssl buildsjoth@chromium.org2011-10-061-3/+7
| | | | | | | | | | | | | Until recently NOTREACHED had no effect (this early in renderer startup) but is now forcing a sad tab. Not using NOTIMPLEMENTED because at this time remoting is intentionally not supported in openssl (see bug) BUG=99163 TEST=Chrome opens when built with use_openssl=1 Review URL: http://codereview.chromium.org/8144002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104257 0039d316-1c4b-4281-b951-d872f2087c98
* CrOS - Speculative fix for shutdown hang talking to zygotejamescook@chromium.org2011-09-301-31/+34
| | | | | | | | | | | ZygoteHost in the browser acquires a lock, sends fork requests to the zygote, then blocks on a read while waiting for a reply with the pid of the forked process. In many error conditions, the zygote never sends a reply to the browser. Now we send back an invalid pid (-1), which ZygoteHost already handles. BUG=chromium-os:20825 TEST=Ensure you can open and close tabs normally. After that, we'll have to watch crash reports. Review URL: http://codereview.chromium.org/8062001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103467 0039d316-1c4b-4281-b951-d872f2087c98
* Fix IPC OnChannelConnected() to send correct PID on Linux/CrOSjamescook@chromium.org2011-08-311-4/+17
| | | | | | | | | | | | | | | | | | | | Sandboxed renderers on Linux/CrOS are in a PID namespace, so they don't know their own global PID. Thus the PID sent in the IPC channel Hello message contains an unexpected value, which is used in the OnChannelConnected() callback into chrome. This causes problems like the Task Manager not showing any data for FPS, JavaScript memory and image cache memory. The task manager is attempting to use the PID/process handle from BrowserMessageFilter, which got it from IPC::Channel::Listener::OnChannelConnected(), and it doesn't match the global PID of each renderer. BUG=70179 TEST=manual, open a few tabs, then open task manager, right-click to turn on JavaScript memory and image memory. Verify there are non-zero values for FPS, JavaScript memory, image cache memory Review URL: http://codereview.chromium.org/7778031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99040 0039d316-1c4b-4281-b951-d872f2087c98
* Remove extensions code from download code. The delegate and other users in ↵jam@chromium.org2011-08-231-1/+1
| | | | | | | | | Chrome can always figure out when a download is for an extension install, instead of storing this data in DownloadItem. I added two new methods to the delegate to allow it to override opening the download item, which allows the chrome layer to install the crx when it completes or is opened. BUG=82782 Review URL: http://codereview.chromium.org/7685046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97899 0039d316-1c4b-4281-b951-d872f2087c98
* linux: undo the seccomp warning I recently addedevan@chromium.org2011-08-041-4/+1
| | | | | | | | | | I had expected this to help track down failing bots, but miraculuously no bots are failing. I have restored the comment to its former form. Review URL: http://codereview.chromium.org/7574012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95444 0039d316-1c4b-4281-b951-d872f2087c98
* linux: turn seccomp on by default in debugevan@chromium.org2011-08-031-1/+4
| | | | | | | | | Print a warning about it on startup for now since I expect some bot somewhere to go bad. Review URL: http://codereview.chromium.org/7570002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95353 0039d316-1c4b-4281-b951-d872f2087c98
* seccomp: refactor logic into a header fileevan@chromium.org2011-08-031-27/+7
| | | | | | | | | I had hoped for this logic to get simpler, but it looks like it needs to be complicated for now. :( Review URL: http://codereview.chromium.org/7465095 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95317 0039d316-1c4b-4281-b951-d872f2087c98
* seccomp: simplify enable/disable logicevan@chromium.org2011-07-291-22/+36
| | | | | | | | | | | | | | 1) Only compile in seccomp code at all if it's on a platform we intend to support (non-ChromeOS non-ARM non-Views Linux). 2) Move usage of seccomp code behind a define and usage of seccomp flags into a function call. The former helps catch bugs in the latter: it will be a link error if I accidentally break the enable/disable logic in code. Review URL: http://codereview.chromium.org/7519016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94784 0039d316-1c4b-4281-b951-d872f2087c98
* Remove explicit keyword from multi-argument (w/o default values) constructorsdilmah@chromium.org2011-07-261-3/+2
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/7477008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94115 0039d316-1c4b-4281-b951-d872f2087c98
* Exit cleanly when sending kZygoteMagic failed.oshima@google.com2011-07-201-1/+2
| | | | | | | | | | | | | | | | ChromeOS may kill chrome right after process starts (when a user closes lid right away for example), and sending magic number to browser process can fail. Instead of CHECK, exit normally on chromeos. BUG=chromium-os:17606 TEST=autotest will not crash with session manager sending SIGTERM Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93171 Review URL: http://codereview.chromium.org/7433011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93222 0039d316-1c4b-4281-b951-d872f2087c98
* Exit cleanly when sending kZygoteMagic failed.oshima@google.com2011-07-201-0/+8
| | | | | | | | | | | | | | ChromeOS may kill chrome right after process starts (when a user closes lid right away for example), and sending magic number to browser process can fail. Instead of CHECK, exit normally on chromeos. BUG=chromium-os:17606 TEST=autotest will not crash with session manager sending SIGTERM Review URL: http://codereview.chromium.org/7433011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93171 0039d316-1c4b-4281-b951-d872f2087c98
* Take two at splitting result codes between content and chrome.dpranke@chromium.org2011-07-191-1/+1
| | | | | | | | | | | | content/common/result_codes.h contains only the codes defined in content. chrome/common/chrome_result_codes.h contains the codes defined in chrome and also includes (for convenience) the content header. R=jam@chromium.org BUG=76699 TEST=everything compiles Review URL: http://codereview.chromium.org/7397004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93082 0039d316-1c4b-4281-b951-d872f2087c98
* Modify the Chrome Linux zygote to support a ZygoteForkHelper for flexiblebradchen@google.com2011-07-181-35/+78
| | | | | | | | | | | | | fork implementations. BUG=nativeclient:480 TEST=existing zygote tests Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=92787 Review URL: http://codereview.chromium.org/7397003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92858 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 92787 - Modify the Chrome Linux zygote to support a ZygoteForkHelper ↵rsleevi@chromium.org2011-07-161-73/+35
| | | | | | | | | | | | | | | | | | | | | for flexible fork implementations. BUG=nativeclient:480 TEST=existing zygote tests Review URL: http://codereview.chromium.org/7397003 TBR=bradchen@google.com Review URL: http://codereview.chromium.org/7400014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92789 0039d316-1c4b-4281-b951-d872f2087c98
* Modify the Chrome Linux zygote to support a ZygoteForkHelper for flexiblebradchen@google.com2011-07-161-35/+73
| | | | | | | | | | | | | | | | fork implementations. BUG=nativeclient:480 TEST=existing zygote tests Review URL: http://codereview.chromium.org/7397003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92787 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r92730, r92731, r92732 ... will land again once I ensure the win ↵dpranke@chromium.org2011-07-151-1/+1
| | | | | | | | | | | | | builds compile. TBR=jam@chromium.org BUG=none TEST= Review URL: http://codereview.chromium.org/7400002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92733 0039d316-1c4b-4281-b951-d872f2087c98
* This change will split the result codes between content and chrome.dpranke@chromium.org2011-07-151-1/+1
| | | | | | | | | | | | | | | This adds a new file into chrome/common and does a lot of renaming. The current version is just a sketch of the headers, and nothing will compile. R=jam@chromium.org BUG=76699 TEST=everything still compiles and runs Review URL: http://codereview.chromium.org/7377010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92730 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 90805 - I am submitting this with LGTMs from agl@ and evanm@. I'm ↵fischman@chromium.org2011-06-281-73/+35
| | | | | | | | | | | | | | | | | | | | | | | marking this as TBR=jam@ because he is on vacation. He previously LGTMed the reverted CL (link below) and there are not substantive changes since then. Modify the Chrome Linux zygote to support a nacl_helper executable, facilitating a special address-space layout as required by NaCl on ARM and ATOM CPUs. In passing, simplify some shared elements of launching NaCl modules in Chrome. This is an update to a previously reverted CL. Please see http://codereview.chromium.org/6995121 for the earlier reviews. Patching nacl_helper CL into fresh branch. BUG=nativeclient:480 TEST=nativeclient in-browser tests TBR=jam@chromium.org TBR=bradchen@google.com Review URL: http://codereview.chromium.org/7230057 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90813 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 90808 - Fixing type error for ZygoteMain.fischman@chromium.org2011-06-281-1/+1
| | | | | | | | | | | | | TBR=agl@chromium.org BUG= TEST= TBR= TBR=bradchen@google.com Review URL: http://codereview.chromium.org/7272031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90812 0039d316-1c4b-4281-b951-d872f2087c98
* Fixing type error for ZygoteMain.bradchen@google.com2011-06-281-1/+1
| | | | | | | | | | TBR=agl@chromium.org BUG= TEST= TBR= git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90808 0039d316-1c4b-4281-b951-d872f2087c98
* I am submitting this with LGTMs from agl@ and evanm@. I'm marking this as ↵bradchen@google.com2011-06-281-35/+73
| | | | | | | | | | | | | | | | | | | | TBR=jam@ because he is on vacation. He previously LGTMed the reverted CL (link below) and there are not substantive changes since then. Modify the Chrome Linux zygote to support a nacl_helper executable, facilitating a special address-space layout as required by NaCl on ARM and ATOM CPUs. In passing, simplify some shared elements of launching NaCl modules in Chrome. This is an update to a previously reverted CL. Please see http://codereview.chromium.org/6995121 for the earlier reviews. Patching nacl_helper CL into fresh branch. BUG=nativeclient:480 TEST=nativeclient in-browser tests TBR=jam@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90805 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 90681 - New NaCl zygote implementation 2, in which Chrome zygote ↵fischman@chromium.org2011-06-281-73/+35
| | | | | | | | | | | | | | | | forks a NaCl helper. This patch can launch earth_c.html with and without the SUID sandbox. It is enabled with the environment variable NACL_NEW_ZYGOTE. BUG=nativeclient:480 TEST=nativeclient in-browser tests on Linux, ChromeOS Review URL: http://codereview.chromium.org/6995121 TBR=bradchen@google.com Review URL: http://codereview.chromium.org/7274011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90682 0039d316-1c4b-4281-b951-d872f2087c98
* New NaCl zygote implementation 2, in which Chrome zygote forks a NaCl helper.bradchen@google.com2011-06-271-35/+73
| | | | | | | | | | | This patch can launch earth_c.html with and without the SUID sandbox. It is enabled with the environment variable NACL_NEW_ZYGOTE. BUG=nativeclient:480 TEST=nativeclient in-browser tests on Linux, ChromeOS Review URL: http://codereview.chromium.org/6995121 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90681 0039d316-1c4b-4281-b951-d872f2087c98
* Get rid of the following dependencies from content:jam@chromium.org2011-06-141-9/+0
| | | | | | | | | | | chrome/common/chrome_constants.h chrome/common/chrome_paths.h chrome/common/logging_chrome.h BUG=76697 Review URL: http://codereview.chromium.org/7104144 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@88935 0039d316-1c4b-4281-b951-d872f2087c98
* Remove content dependency on ↵jam@chromium.org2011-06-131-1/+1
| | | | | | | | | chrome/browser/accessibility/browser_accessibility_state.h and chrome/common/chrome_switches.h. BUG=76697,85932 Review URL: http://codereview.chromium.org/7046114 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@88923 0039d316-1c4b-4281-b951-d872f2087c98
* Replace OS_LINUX ifdefs with OS_POSIX & !OS_MACOSX, TOOLKIT_USES_GTK, ortony@chromium.org2011-05-311-10/+15
| | | | | | | | | | | USE_X11 where possible. An earlier version of this patch was used to build Chromium on FreeBSD, OpenBSD, and Solaris. Patch by ruben (chromium@hybridsource.org) Review URL: http://codereview.chromium.org/7006006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87382 0039d316-1c4b-4281-b951-d872f2087c98
* Move PepperPluginRegistry to content, while leaving the Chrome specific bits ↵jam@chromium.org2011-04-181-1/+1
| | | | | | | | (NaCl, registration of Chrome plugins like pdf/remoting/flash) behind. Review URL: http://codereview.chromium.org/6869051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81959 0039d316-1c4b-4281-b951-d872f2087c98
* Move crypto files out of base, to a top level directory.rvargas@google.com2011-04-141-2/+2
| | | | | | | | | | | | | src/crypto is now an independent project that contains our cryptographic primitives (except md5 and sha1). This removes the base dependency from nss, openssl and sqlite. BUG=76996 TEST=none Review URL: http://codereview.chromium.org/6805019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81611 0039d316-1c4b-4281-b951-d872f2087c98
* Move some files from base to base/memory.levin@chromium.org2011-03-281-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | raw_scoped_refptr_mismatch_checker.h ref_counted.cc ref_counted.h ref_counted_memory.cc ref_counted_memory.h ref_counted_unittest.cc scoped_callback_factory.h scoped_comptr_win.h scoped_handle.h scoped_native_library.cc scoped_native_library.h scoped_native_library_unittest.cc scoped_nsobject.h scoped_open_process.h scoped_ptr.h scoped_ptr_unittest.cc scoped_temp_dir.cc scoped_temp_dir.h scoped_temp_dir_unittest.cc scoped_vector.h singleton.h singleton_objc.h singleton_unittest.cc linked_ptr.h linked_ptr_unittest.cc weak_ptr.cc weak_ptr.h weak_ptr_unittest.cc BUG=None TEST=Compile Review URL: http://codereview.chromium.org/6714032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79524 0039d316-1c4b-4281-b951-d872f2087c98
* Increase message size for the zygote channelpiman@google.com2011-03-231-1/+1
| | | | | | | | | | | | | Increasing renderer command-line size leads to problems. This is a temporary work-around, but a long term solution is needed. BUG=chromium-os:13289 TEST=before patch, increase renderer command line size to about 1k, observe the hangs. apply patch, observe no hang with same command line. Review URL: http://codereview.chromium.org/6733001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79177 0039d316-1c4b-4281-b951-d872f2087c98
* Guards "remoting" initialization on the renderer side.bulach@chromium.org2011-03-181-2/+4
| | | | | | | | | | | | | Following http://codereview.chromium.org/6684018, remoting requires NSS to be initialized in the render side. This change allows to compile with openssl. BUG=none TEST=compiles with use_openssl=1 Review URL: http://codereview.chromium.org/6665065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78681 0039d316-1c4b-4281-b951-d872f2087c98
* Move the renderer_web* files to content.jam@chromium.org2011-03-181-1/+1
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6713024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78643 0039d316-1c4b-4281-b951-d872f2087c98
* Load additional NSS library files in zygote main if remoting is enabledhclam@google.com2011-03-171-13/+6
| | | | | | | | | | | | | | Instead of initializing NSS before the sandbox is engaged this loads the necessary additional libraries for NSS to function properly. This allows initializing NSS after sandbox is closed and solve the security problem of loading NSS early. BUG=None TEST=None Review URL: http://codereview.chromium.org/6672034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78633 0039d316-1c4b-4281-b951-d872f2087c98
* Move media library path resolution into Chrome path provider.wez@chromium.org2011-03-171-3/+7
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/6537022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78532 0039d316-1c4b-4281-b951-d872f2087c98
* Move the remaining files in chrome\common to content\common.jam@chromium.org2011-03-171-4/+4
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6672070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78516 0039d316-1c4b-4281-b951-d872f2087c98
* Move a bunch of files from chrome\common to content\common.jam@chromium.org2011-03-171-2/+2
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6677096 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78473 0039d316-1c4b-4281-b951-d872f2087c98
* Initialize NSS with no DB in the renderer processhclam@google.com2011-03-161-0/+15
| | | | | | | | | | | | | | | | | | | | | This change will allow the use of SSLClientSocketNSS to be used in the renderer process. This is needed by chromoting client to establish SSL connections. There are several concerns that are cleared: 1. NSS_NoDB_Init() does open user's cert DB and user modules. 2. NSS_NoDB_Init() doesn't keep file descriptors open. It tries to open /pkcs11.txt and /secmod.db which is a bug and filed: https://bugzilla.mozilla.org/show_bug.cgi?id=641052 However the above bug is not considered harmful. BUG=75834 TEST=None Review URL: http://codereview.chromium.org/6684018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78317 0039d316-1c4b-4281-b951-d872f2087c98
* Move some chrome\common code to content in preparation for moving chrome\gpu.jam@chromium.org2011-03-111-1/+1
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6686002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77868 0039d316-1c4b-4281-b951-d872f2087c98
* Move content specific switches to content, in preparation for moving ↵jam@chromium.org2011-03-031-3/+6
| | | | | | | | | directories that currently depend on common (like gpu). TBR=bradnelson Review URL: http://codereview.chromium.org/6603011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76785 0039d316-1c4b-4281-b951-d872f2087c98
* Move the rest of the core files in chrome\browser to content\browser.jam@chromium.org2011-02-231-0/+753
TBR=avi Review URL: http://codereview.chromium.org/6538111 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@75711 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-26 17:32:06 +0000