| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
disabled code for OpenBSD:
- AdjustRendererOOMScore()
- SECCOMP_SANDBOX
BUG=
TEST=compile
Review URL: http://codereview.chromium.org/8341052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109679 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Original CL http://codereview.chromium.org/8368018/ was sort of
aggressive in some areas. I reveiewed it and this pulls back the
cases I'm pretty sure should be kept. My basic approach was to keep
things which would probably never happen in development, and which
signal a problem which is unlikely to be transient.
- important_file_writer.cc getting impossible amounts of data.
- cfbundle_blocker.mm logs blocked bundles so user can see.
- objc_zombie.mm crashes if the objc runtime is unexpectedly bizarre.
- multi-process lock logs failure.
I've actually seen that last before when a test nested a profile too
deeply, in which case knowing the filename was the key hint.
Review URL: http://codereview.chromium.org/8477018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109080 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8368018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107814 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
| |
BUG=NONE
TEST=BUILD
Review URL: http://codereview.chromium.org/5113006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66964 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
Platform abstraction for a shared lock between processes. The process
that owns the lock will release it on exit even if exit is due
to a crash.
For cloud-print and remoting we want to be able to have a singleton service-process that can run independently of the browser process. This service process will communicate with the browser process via the standard IAC channels, but we want to have a way of signaling to other processes that a) there is a service-process running and b) that it is in a state where it is ready to be communicated with. The multi_process_lock class is intended to work as a simple flag that can be queried from multiple processes. If the service-process should crash, we would like the flag to be cleared automatically so that there is never confusion about the state of the service-process.
Other approaches considered for some Unix/Mac:
- Standard unix domain sockets depend on the file system and don't clean up properly in the case of a crash.
- Shared memory on unix depend on the file system and don't clean up properly in the case of a crash.
- System V semaphores on unix again depend on the file system.
- named_mach_ports on Mac OS. Bootstrap_register_name has been deprecated on 10.6, so we are doing essentially the same thing using CFMessagePort.
On Windows it is implemented as an event.
On Mac it is implemented using a CFMessagePort name.
On Linux it is implement using an abstract name port socket.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/4721001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66323 0039d316-1c4b-4281-b951-d872f2087c98
|
