- 5be8f34 Fix 64-bit warnings (for 64-bit Windows build) by gregoryd@google.com · 15 years ago
- 3ac3206 reland 31875. Revert was: by estade@chromium.org · 15 years ago
- 9e31fcd Revert 31875 to see whether it fixes reliability bot. by huanr@chromium.org · 15 years ago
- 64997aa Use renderer spellchecker for windows. by estade@chromium.org · 15 years ago
- b1f47b2 First patch in making destructors of refcounted objects private. by jam@chromium.org · 15 years ago
- 21ae481 GTK: Properly convert task manager UI row to task manager model row. by estade@chromium.org · 15 years ago
- 5863a19 Add the ability for objects which derive from RefCountedThreadSafe to specify a destructor trait. This allows browser objects to specify which thread they're terminated on. The benefit is we avoid the need to do manual ref counting when an object posts tasks to itself on different threads, if an object must be destructed on a specific thread. by jam@chromium.org · 15 years ago
- 03100a8 Suppress a data race on vfptr in ipc/ipc_sync_channel_unittest.cc by timurrrr@chromium.org · 15 years ago
- 7cd41eb Move the json-related files into a separate json directory. This hopefully also by brettw@chromium.org · 15 years ago
- 7d3eaa7 linux: cut down on EPIPE error spew by evan@chromium.org · 15 years ago
- 44aaf62 Linux: remove the pipe errors that we spew all the time. by agl@chromium.org · 15 years ago
- 2777cb0 The send done event in the old send watcher can be NULL as it can be signaled in a nested sync channel by ananta@chromium.org · 15 years ago
- 31b338f John, please review everything. by ananta@chromium.org · 15 years ago
- 90a3f8a Eliminate all uses of strerror() in code that uses src/base. strerror() is inherently unsafe in multi-threaded apps because it stores the string in a global buffer. It should never be used. If you want to log an error, use PLOG and friends, or if that's too high-level then use safe_strerror(). by tschmelcher@chromium.org · 15 years ago
- e3fca69 Use ASCII strings for switch names. by evan@chromium.org · 15 years ago
- a52632f Move more ICU-dependent stuff from base into base/i18n. Some test stuff also by brettw@chromium.org · 15 years ago
- 554d431 Modify extension request IPC messages to pass a ListValue instead of a string. by mpcomplete@chromium.org · 15 years ago
- 5cb996e Reverting 27389. Review URL: http://codereview.chromium.org/246027 by darin@chromium.org · 15 years ago
- ddf7151 First step towards NaCl-Chrome integration:1. NaCl plugin becomes a built-in plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "--internal-nacl" is required to enable the built-in NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandboxCommitted: http://src.chromium.org/viewvc/chrome?view=rev&revision=27315 by gregoryd@google.com · 15 years ago
- f2b21be Implement about:ipc dialog for Mac. by jrg@chromium.org · 15 years ago
- 5673222 Revert 27397 - First step towards NaClChrome integration:1. NaCl plugin becomes a builtin plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "internalnacl" is required to enable the builtin NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandboxCommitted: http://src.chromium.org/viewvc/chrome?view=rev&revision=27315 by gregoryd@google.com · 15 years ago
- 2b7b017 First step towards NaCl-Chrome integration:1. NaCl plugin becomes a built-in plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "--internal-nacl" is required to enable the built-in NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandboxCommitted: http://src.chromium.org/viewvc/chrome?view=rev&revision=27315 by gregoryd@google.com · 15 years ago
- 983005a Reverting 27379, in hopes of fixing browser_tests. by senorblanco@chromium.org · 15 years ago
- f35c179 Assert that thread-safe reference counting is used with by darin@chromium.org · 15 years ago
- 1b72200 Revert 27324 - First step towards NaClChrome integration:1. NaCl plugin becomes a builtin plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "internalnacl" is required to enable the builtin NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandboxCommitted: http://src.chromium.org/viewvc/chrome?view=rev&revision=27315 by gregoryd@google.com · 15 years ago
- 463aec4 First step towards NaCl-Chrome integration:1. NaCl plugin becomes a built-in plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "--internal-nacl" is required to enable the built-in NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandboxCommitted: http://src.chromium.org/viewvc/chrome?view=rev&revision=27315 by gregoryd@google.com · 15 years ago
- 167ebb7 Revert 27315 - First step towards NaClChrome integration:1. NaCl plugin becomes a builtin plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "internalnacl" is required to enable the builtin NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandbox by gregoryd@google.com · 15 years ago
- 385f77a First step towards NaCl-Chrome integration:1. NaCl plugin becomes a built-in plugin in Chrome and runs in the renderer process.2. Most of the changes are related to launching the NaCl process (that loads and runs the NaCl module) and establishing the initial communication between that process and the NaCl plugin.3. Command line flag "--internal-nacl" is required to enable the built-in NaCl plugin. NaCl still cannot run in Chrome sandbox, the flag automatically disables the sandbox by gregoryd@google.com · 15 years ago
- 2f74d1c Fix reads and writes to freed memory in Channel::ChannelImpl::OnFileCanReadWithoutBlocking() by hawk@chromium.org · 15 years ago
- fa6a75b IPC & LibEvent fix by jeremy@chromium.org · 15 years ago
- 9d45f48 Preparing rollback in case things don't work out. by bradnelson@google.com · 15 years ago
- 9435be7 This is a copy of http://codereview.chromium.org/153002/show by gregoryd@google.com · 15 years ago
- a81f84a On Linux, move the passing of filedescriptors to a dedicated socketpair(). by agl@chromium.org · 15 years ago
- 1507065 Revert "Fix a ton of compiler warnings." by tony@chromium.org · 15 years ago
- 2c3262c Fix a ton of compiler warnings. by estade@chromium.org · 15 years ago
- 6718e58 Speculative fix for a leak in SyncChannel. by jeremy@chromium.org · 15 years ago
- 3a2fc8c Add a nullable string16 class to base. It combines a string16 + a null param by jorlow@chromium.org · 15 years ago
- b818a7e Recommit "Bring up Firefox Password Import Unittest on OS X." by jeremy@chromium.org · 15 years ago
- ad8ced5 Revert "Bring up Firefox Password Import Unittest on OS X." by jeremy@chromium.org · 15 years ago
- 9f8d41e Bring up Firefox Password Import Unittest on OS X. by jeremy@chromium.org · 15 years ago
- 1605b6d Implementation of getBackgroundPage(), getToolstrips(), and getTabContentses(). by aa@chromium.org · 15 years ago
- 0aa0502 Cross-process Message Port implementation. by jam@chromium.org · 15 years ago
- 1c86b55 The messages attached to the task created by an IPC ChannelProxy are leaked when the message loop is destroyed (the MessageLoop deletes its pending tasks on destruction, but not the messages). by jcampan@chromium.org · 15 years ago
- 1543aa7 Fix the massive type confusion for ParamTraits in the IPC code. by deanm@chromium.org · 15 years ago
- 4bdd5df posix: cut down on IPC logging spew a bit by evan@chromium.org · 15 years ago
- a659036 posix: handle chars more delicately in ipc logging by evan@chromium.org · 15 years ago
- c12dde3 Unrevert 21355 because the revert might be causing the worker tests failures. by nsylvain@chromium.org · 15 years ago
- 3050ba6 Build fix: I incorrectly applied r21399 from a patch. by agl@chromium.org · 15 years ago
- 030b1b5 Revert 21355 because it might be causing all the new by nsylvain@chromium.org · 15 years ago
- e949174 Switch the first thread in a child process to be the main thread, and make theIO thread be the second thread. The change is needed for plugins on mac. by jam@chromium.org · 15 years ago
- 1c6dcf2 Split the IPC code into ipc/ by agl@chromium.org · 15 years ago
- 9f96682 Revert "Move IPC code to ipc/" by agl@chromium.org · 16 years ago
- 2390c8c Move IPC code to ipc/ by agl@chromium.org · 16 years ago