Does this mean the zygote manager process is the parent process for the browser process and all renderer processes? Whereas before the browser process was the parent to all renderer processes.
On Mon, Jun 8, 2009 at 5:39 PM, Dan Kegel<daniel.r.ke...@gmail.com> wrote: > > http://src.chromium.org/viewvc/chrome?view=rev&revision=17909 enabled > zygote mode on Linux by default. This changes how processes > work on Linux; the initial process becomes a fork server, > and holds open file descriptors for the .pak files. > This lets us continue running even if the app is > updated or uninstalled while we're running. The > next time you restart, the new files will take effect. > > If for some reason (say, you don't like the fact that the > main process is now this funky fork server) you want to > go back to how things were before temporarily, > you can disable zygote mode by doing > export DISABLE_ZYGOTE_MANAGER=x > before running. > > The valgrind ui_test bots are currently greener than they should > be, possibly because zygote mode is interfering with > how I set ui_test mode up under valgrind. I'll have a > look at that tomorrow. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
