We limit to 4Gb because certain types of attacks rely on being able to allocate > 4Gb of memory.
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/ede933c9-d623-40cb-8633-50b2256f7828%40chromium.org.
Thank you for your reply and information.I did not know much about Chromium's architecture and your reply was so helpful.Although I could not find the document that question, so I look up code, the amount allocated memory to the renderer process for Windows seems to match 2 GB. (I cannot read Objective-c or c++ code, so may be wrong...)src/sandbox/win/src/sandbox_nt_util.cc
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAHOzFCBqTHysf2vn836UqPhNsLsX3Fb8a5kAikxXki3S7GEYw%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/51661fa0-6e68-458f-ab09-8ab9c4c18164%40chromium.org.
It is possible you get a bit more memory into a process that way, but if anyone wants to remove the 2 GB/32-bit limit completely there is probably a lot of places that need to change. Another place (of many) is PartitionAlloc, a commonly used internal allocator (what yutak called Blink memory allocator). It's just been an implicit 2 GB limit for so long that it is impossible to know how many places that implicitly or explicitly depend on it.Eventually this limit might have to be addressed, but for now it also acts as a protection against runaway sites. Nothing prevents a site from allocating memory, but if they try to allocate more than 2 GB that will kill the renderer which is at least better than consuming all the RAM in the machine.If there was some particular operation a site did that accidentally hit the limit, the first approach would be to try to reduce its memory usage. [Looking at Google Docs/Sheet/Whatever]/Daniel
To unsubscribe from this group and stop receiving emails from it, send an email to chromi...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/51661fa0-6e68-458f-ab09-8ab9c4c18164%40chromium.org.
This is outrageous. How astonishingly shortsighted. I specifically bought the new MacMini with 64GB of RAM so that I wouldn't have these problems of tabs crashing, as I'm a tab hoarder and sites like Facebook with heavy javascript usage are gluttons for RAM -- but I can increase the supply of resources rather than waiting for sites to be more efficient with their code. Moore's Law in action. Or as George Gilder said, "waste transistors". Humans are expensive and hardware is cheap.There truly is no way to recompile Chrome / Chromium to lift these hard limits? I can always expand how much RAM I have, but I cannot abide tabs crashing.
Renderer
GPU
Windows, Linux: 64 GiB (less if less system memory)
Network
Windows: 16 GiB
Other Utilities
Windows: 16 GiB via default policies
Browser
None