644004 - "out of memory" due to GC, despite lots of physical memory left

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Alon Zakai (:azakai)]

The attached archive contains emscripten and a very large input file for it (poppler+freetype), which when run as follows

  js compiler.js < src.cpp.o.ll

will run for a while, reach approx 600MB of virtual and resident memory, then exit with "out of memory". This is triggered due to

  delayedOutOfMemory = (rt->gcBytes > rt->gcMaxBytes)

in jscntxt.cpp. gcMaxBytes is 160MB, and gcBytes reaches it.

There is, however, over 2GB of free physical memory on this machine.

v8 runs the script successfully, reaching a maximum of about 400MB.

Comment 1

[Alon Zakai (:azakai)]

Attachment was too big for bugzilla. Here it is:

http://syntensity.com/static/src.tar.bz2

Comment 2

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Can you try this at the top of the script?
  gcparam('maxBytes', 1024*1024*1024);

For some reason, gcMaxBytes is set to be pretty low in the shell. It's much higher in the browser.

Comment 3

[Alon Zakai (:azakai)]

Thanks, that fixes it.

Is it feasible to make it so we can allocate any amount of memory for GC (while there is system memory)?