Firefox behaves terribly upon update on Linux because they didn't bother even trying to make distro updates work well, and everybody uses distro packages for Firefox. Let's avoid this same problem on Chrome for Linux. Does that sound like a reasonable goal? We're early enough in the port that it might not be too hard to bake that feature in.
What would it take to survive all our files changing out from under us? I imagine it would suffice to: 1) open all the files we're going to need early, and keep the handles around for when we need them 2) for our own executables, don't exec, only fork. That would mean using a zygote, i.e. at startup time, fork before creating any threads, and have the initial instance just be a factory for anybody who needs another instance of that executable. Is that practical, and did I miss anything? - Dan --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
