Comment #1 on issue 15847 by [email protected]: Dynamically rebase chrome.dll on a system-specific way http://code.google.com/p/chromium/issues/detail?id=15847
About the problem: I would avoid doing this until you understand the interaction with ASLR. (Vista and Win7 and some versions of server). ASLR implementations should share rebasing info across processes to avoid exactly the problem you describe. I don't know the details, but I understand the OS reporting of shared vs private memory can be misleading (there are differences in how XP, Vista and Win7 report these numbers in taskman) Do we know for sure if chrome.dll is being rebased for reasons other than ASLR? i.e. what data do we have to support the premise? Do we know why it happens? If the premise is true (no choice of base address avoids rebasing on certain machines), do we know if it is machine specific (rebasing might help) or if each process requires a different load address? About the differential installer: chrome.dll is diffed while it is still inside the download archive, it is actually chrome.7z that is diffed. So it would be unnecessary to change the install, which is good because it would be too difficult to make the diff work against an arbitrarily rebased dll. -- 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 -~----------~----~----~----~------~----~------~--~---
