Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upincrease max old space size not working #14590
Closed
Comments
|
/cc @nodejs/v8 |
|
All three runs fail with an error, don't they? Is the bug report here that the second one fails with "invalid table size" instead of "out of memory"? That's because collections have a maximum size (512 MB on 32 bits architectures, 1 GB on 64 bits, IIRC.) |
|
Seems like it should throw a JS exception on invalid size instead of a hard crash though. |
|
You'd have to take that up with the V8 team. It's not just maps and sets though; arrays have similar size limits. |
|
I'll close this out. If anyone feels the current behavior isn't what it should be, please file an issue or CL with V8. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run this code:
Result:
I used the flag to increase the maximum memory
--max-old-space-size=2000but it had no effectBut if add console.log to body:
then flag --max-old-space-size working: