Status: Unconfirmed Owner: [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 4812 by beng331: Make some sense of the startup sequence http://code.google.com/p/chromium/issues/detail?id=4812 The startup sequence is somewhat haphazardly split across chrome_dll_main.cc, browser_main.cc and browser_init.cc. There are huge multi-page functions where everyone and their dog hook in and do startup. We should have an observer system whereby modules can register as observers of various points during startup. This will make our startup process more understandable and allow more of our codebase to be reused. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
