Status: Untriaged Owner: [email protected] CC: [email protected], [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 8102 by [email protected]: Make pak files resilient against overwriting / updating. http://code.google.com/p/chromium/issues/detail?id=8102 We currently load pak files as a shared memory mapping that isn't private. I believe this means that if the files were to be changed on disk, they would be changed in our running chrome also. We should make it so these files can be replaced (updated, for example) without affecting currently running instances (much like how replacing the binary would work). -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
