Google Git
Sign in
chromium / chromium / src / d87f8e6f287c0c8a79cf18e13a7c6debd3a77bb3 / chrome / common / child_process_info.h
  1. 709a847e Implement a new process type for running PPAPI plugins. The process itself is by [email protected] · 15 years ago
  2. 41b5c20 Convert a couple of wstring methods in ChildProcessInfo. by [email protected] · 15 years ago
  3. 32b76ef `#pragma once` for app, base, chrome, gfx, ipc, net, skia, views by [email protected] · 15 years ago
  4. 7e3ceeb4 Adds the plugin version on the title. This shows up in task manager: by [email protected] · 15 years ago
  5. 103607e Implement the broker process that launches NaCl loader processes on 64-bit Windows systems. by [email protected] · 16 years ago
  6. 0b6e0a2 Revert 37578 - Implement the broker process that launches NaCl loader processes on 64bit Windows systems. by [email protected] · 16 years ago
  7. 08aab35 Implement the broker process that launches NaCl loader processes on 64-bit Windows systems. by [email protected] · 16 years ago
  8. c0fc094 Add the ability for the GPU process to be used to paint the backing store of a by [email protected] · 16 years ago
  9. 1f08562 Improve reporting of subprocess crashes. by [email protected] · 16 years ago
  10. 57a336a Remove all MemoryModel-related code, since we're unlikely to use it again. Also changes some sample code to use a random generic name ("PruningAlgorithm") instead of MemoryModel in hopes that no one will be confused. by [email protected] · 16 years ago
  11. d032f49 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 [email protected] · 16 years ago
  12. 63c8147e 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 [email protected] · 16 years ago
  13. 6affd92 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 [email protected] · 16 years ago
  14. 8939b46c 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 [email protected] · 16 years ago
  15. 08127f5 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 [email protected] · 16 years ago
  16. 37e1bb6 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 [email protected] · 16 years ago
  17. 08a3ef6 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 [email protected] · 16 years ago
  18. 2735e369 Misc. Cleanup related to OOP Profile Import by [email protected] · 16 years ago
  19. 79970a2cf Preparing rollback in case things don't work out. by [email protected] · 16 years ago
  20. ea5ac0e This is a copy of http://codereview.chromium.org/153002/show by [email protected] · 16 years ago
  21. 54fd1d3 Linux: about:memory by [email protected] · 16 years ago
  22. 76543b9c Replace the RenderProcessHost.PID function that returns the OS-generated by [email protected] · 16 years ago
  23. 9a3a293b ipc: use strings, not wstrings for channel ids. by [email protected] · 16 years ago
  24. 1fca149 Introducing the Utility process, which handles the unpacking and verification by [email protected] · 16 years ago
  25. fd099503 Finish hooking up the worker process UI: use the domains of the workers as the title in the task manager, and show an infobar when a page's workers die. by [email protected] · 16 years ago
  26. dc993e3 Fix single-process ui test failures from my previous change. The problem was that the wrong pid was being sent to RDH from RMF. It needs to be the fake pid for the in-process renderer. by [email protected] · 16 years ago
  27. dabe607 Hide the details about ResourceDispatcherHost messages from child processes. The usage of RDH is now like RD, the client sends the message to RDH to see if it should handle it. I added methods to the Receiver interface so that RDH can get to the process id/handle/type when starting requests. by [email protected] · 16 years ago
  28. 319d9e6f Reduce the amount of included header files. Vast change like in "Oh God! This revision changes half of the source files!". by [email protected] · 17 years ago
  29. 6dffde32 Take out common functionality from PluginProcessHost and move it to ChildProcessHost. by [email protected] · 17 years ago
  30. a16ed65e NO CODE CHANGE. by [email protected] · 17 years ago
  31. a436d92 Have ChildProcessInfo contain a list of all running child processes (i.e. instead of Service and other child process service maintain it). In a future change I'll start moving some of the code from PluginProcessHost to ChildProcessInfo. by [email protected] · 17 years ago
  32. a27a938 Refactor plugin process code in the browser process so that the browser/about:memory/task manager/metrics code doesn't depend on PluginProcessHost pointers. In a future changelist I'll add one central child process registry in the browser process. by [email protected] · 17 years ago