Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to increase or remove heap memory limit #2600

Open
1 task
kzhsw opened this issue Nov 9, 2023 · 2 comments
Open
1 task

Option to increase or remove heap memory limit #2600

kzhsw opened this issue Nov 9, 2023 · 2 comments

Comments

@kzhsw
Copy link

kzhsw commented Nov 9, 2023

Description

Make an option, in flags or command-line, to allow users to increase or remove heap memory limit, to use heap larger than 4GB in systems with much greater memory.

Who's implementing?

  • I'm willing to implement this feature myself

The problem

Currently chrome limits the heap memory (or the memory of a render process) to likely 4GB, but larger heap would be useful for debugging heap using the memory profiler, or running large, resource-consuming app on web.
This is previously discussed on many forums, but now I can not find a thing that works without rebuilding the chromium itself.

Previous contexts:

Possible solutions

  • Make the flag --max-old-space-size and --max-semi-space-size work like in node.js
  • Make a flag to disable pointer compression (this could be a compile-time flag)
  • Get things upstreamed

Alternatives

Use Firefox which has larger limit on heap, and a slower js engine.

Additional context

No response

@richard-stafflink
Copy link

Haven't tested it, but does this work:

chrome --js-flags="--max_old_space_size=8192"

@kzhsw
Copy link
Author

kzhsw commented Feb 26, 2024

Haven't tested it, but does this work:

chrome --js-flags="--max_old_space_size=8192"

This could increase limit for ArrayBuffers, but not js objects, nor postMessage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants