4GB memory usage limit for Chrome process (64-bit)

944 views
Skip to first unread message

Edgar

unread,
Dec 15, 2014, 8:27:59 PM12/15/14
to chromium...@chromium.org
Is there a way to increase the 4GB limit per tab e.g. via a command line switch? I see (from Process Explorer) that each Chrome (64-bit) tab process, also the internal Chrome GPU process, is artificially limited to a max of 4GB RAM usage via Windows Job limits. We are developing a single page web app that uses WebGL, we'd like to be able to use more than 4GB of RAM.

I see in this post https://code.google.com/p/chromium/issues/detail?id=416284#c5 that the 4GB limit is by design, due to security issues, ".. because certain types of attacks rely on being able to allocate > 4Gb of memory...". Can anyone elaborate more on what those types of attacks are, and whether there's any chance that this limitation will be lifted in the future, or temporarily disabled via command line switch, at least for the Chrome internal GPU process. Thanks!


yujian221

unread,
Dec 16, 2014, 7:18:08 PM12/16/14
to chromium...@chromium.org
I want to download the release 38.0.2078.0. For rescue time, I change the .gclient file as following because I won't download LayoutTests. LayoutTest is too big. But when I use the command (gclient sync --force)to get the source code, I found that it get LayoutTest project. Does anyone know why?

solutions = [
  { "name"        : "38.0.2078.0",
    "url"         : "http://src.chromium.org/svn/releases/38.0.2078.0",
    "deps_file"   : "DEPS",
    "managed"     : True,
    "custom_deps" : {
      "src/third_party/WebKit/LayoutTests": None,
      "src/chrome_frame/tools/test/reference_build/chrome": None,
      "src/chrome/tools/test/reference_build/chrome_mac": None,
      "src/chrome/tools/test/reference_build/chrome_win": None,
      "src/chrome/tools/test/reference_build/chrome_linux": None,
      "chromeos": None,
      "depot_tools": None,
    },
    "safesync_url": "",
  },
]
cache_dir = None

Torne (Richard Coles)

unread,
Dec 17, 2014, 6:12:36 AM12/17/14
to yuji...@gmail.com, Chromium-discuss
The suggestion to set LayoutTests to None in custom_deps is obsolete and only works with svn checkouts, which are no longer possible as the main repo has switched to git. Git does not support downloading only part of a repository; there is no way to exclude LayoutTests any more.

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

Christian Biesinger

unread,
Dec 18, 2014, 7:03:47 PM12/18/14
to Torne (Richard Coles), yuji...@gmail.com, Chromium-discuss
However, you can try "fetch --no-history" (or gclient sync
--no-history) if you don't care about all the historical data.

-christian

yujian221

unread,
Dec 22, 2014, 10:33:53 AM12/22/14
to Christian Biesinger, Torne (Richard Coles), Chromium-discuss
Thanks, I will try it.
Reply all
Reply to author
Forward
0 new messages