+1 Please do not remove it. It is VERY valuable for development and debugging across renderer and browser. IMO, it should be maintained at least enough to mostly run (at least past startup as shown above). If this startup failure can be reproduced, it should be filed as a bug and fixed. I have less sympathy for very complex examples, but could convinced otherwise. Jim
On Fri, Jun 5, 2009 at 8:59 AM, Evan Martin <[email protected]> wrote: > > On Fri, Jun 5, 2009 at 7:37 AM, Marc-Antoine Ruel<[email protected]> > wrote: > > --single-process is not maintained and its tests have been downgraded to > the > > "For Your Information" waterfall > > at http://build.chromium.org/buildbot/waterfall.fyi/waterfall > > We'd probably accept patches to simply remove it or to fix it but I guess > > removing it will reduce confusion. > > It's really useful for working on multiproc stuff like plugins (which > involve messages between three subprocesses). I don't think we want > to remove it, but I believe we have already disabled it in user > releases because it's very fragile. > > To answer the original question: the mistake the developer had done > was to think --single-process worked. ;) > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
