-
Notifications
You must be signed in to change notification settings - Fork 198
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
Chromium 129.0.6668.100 compile fails at the very end during linking with std::bad_alloc error #845
Comments
I've been seeing this issue in my builds for the last few releases, but @SoumyaWind was able to build fine. Maybe it's time to actually submit a bug report to LLVM as suggested in the output. Would it be possible for you to do that? |
On my side also meet the same issue on NXP imx boards |
I ran into this too, the issue is the kernel's limit on the number of memory mappings each process is allowed to create: https://docs.kernel.org/admin-guide/sysctl/vm.html#max-map-count You can set the limit to a larger number easily, just run this as root:
To make it permanent, add this to /etc/sysctl.conf:
|
I was running into this problem too. Increasing the |
Thanks for finding the fix! |
This adds a section to the readme, explaining the solution to a build error discussed in OSSystems#845. Adding this in the readme makes it easier to be found. Signed-off-by: Matthias Schoepfer <[email protected]>
This adds a section to the readme, explaining the solution to a build error discussed in OSSystems#845. Adding this in the readme makes it easier to be found. Signed-off-by: Matthias Schoepfer <[email protected]>
This adds a section to the readme, explaining the solution to a build error discussed in OSSystems#845. Adding this in the readme makes it easier to be found. Signed-off-by: Matthias Schoepfer <[email protected]>
This adds a section to the readme, explaining the solution to a build error discussed in OSSystems#845. Adding this in the readme makes it easier to be found. Signed-off-by: Matthias Schoepfer <[email protected]>
Hi,
Chromium 129.0.6668.100 compile fails at the very end during linking with std::bad_alloc error. Built this using meta-clang styhead branch. We tried to build on a machine with high memory but it still failed.
Did anyone run into this issue ? Any help would be much appreciated.
The text was updated successfully, but these errors were encountered: