On Thu, Sep 17, 2009 at 6:25 PM, Marc-Antoine Ruel <[email protected]>wrote:
> > There are issues with the sandbox because it is creating the renderer > and plugin processes in a job object. > > I recall runas has issues too because of the CREATE_BREAKAWAY_FROM_JOB > flag is not working. > This is right. When you create your job you need to set the basic limit flag JOB_OBJECT_LIMIT_BREAKAWAY_OK. The renderer processes won't be in your job (since it's not possible to be in 2 jobs at the time, and the sandbox needs to control its own job), but the browser process and the plugin processes will be in your job. If it does not work, feel free to post what kind of restrictions you are using on your job, and we'll take a look. Nicolas > > You may want to try to disable the job object functionality of the > sandbox but I'm not sure this is what you want either. > > M-A > > On Thu, Sep 17, 2009 at 9:11 PM, Daniel Cowx <[email protected]> > wrote: > > > > To be clear, I don't want to run within a job **only** so I can be > > notified of exit (obviously I could do this with a handle), so please > > don't suggest that I do that instead <wink>. What I am looking for is > > a solution to how I can run not only the sandboxed target processes, > > but also the main broker process within a job. > > > > Thanks, > > Daniel > > > > On Sep 17, 5:58 pm, Daniel Cowx <[email protected]> wrote: > >> I'd like to run chromium (the broker) within a Windows job so that I > >> can be notified when it exits. Does anyone know if this is possible? > >> My preliminary testing (with a job that imposes no limits whatsoever) > >> is causing problems unless I use the "no-sandbox" or "single-process" > >> flags; which is not what I want to do. Thoughts? > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
