For single process mode add --single-processto the command line when launching Chrome. Please note that this mode is _only_ for testing during development and there are known things that will break, which we most likely know about and do not plan to fix. We make no guarantees that things will work in this mode and regular users should _NOT_ use this mode. If you come across issues while using this mode, reproduce them without this flag before filing as bugs.
As for the checklist to build faster, I would search the archives because I remember Marc-Antoine (maruel of chromium org) sending an email with this information. Don't remember his list off hand. -F On Tue, Feb 10, 2009 at 18:05, eager_learner <[email protected]>wrote: > > Hello > > I am in the process of writing my "internal" plugin until plugin API > are made public in May (as per posts). > > My plugin gets invoked correctly but I had to find out the hardway. > For kicks, I put in code that would assert using an illegal operation > in the NPAPI and observed the crash. I remember reading something > about running chrome in the single process mode. I cant seem to find > it among the million bookmarks that I have. Does anyone have > instructions for that? > > Also despite a dual core processor with 1GB ram build and debug is > painfully slow. Does anyone know of a check list of things that can be > disabled to speed the build? > > Thanks > PS> Here is a need for a tool that parses bookmark urls, titles and > the pages and keeps a local PC database so that searching bookmarks is > not tougher than just googling ... > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
