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

Chromium 129.0.6668.100 compile fails at the very end during linking with std::bad_alloc error #845

Closed
neenareddi opened this issue Oct 31, 2024 · 5 comments

Comments

@neenareddi
Copy link

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.

image-2024-10-25-16-25-58-156

Did anyone run into this issue ? Any help would be much appreciated.

@MaxIhlenfeldt
Copy link
Collaborator

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?

@WujianSun
Copy link

On my side also meet the same issue on NXP imx boards

@jcalvinowens
Copy link

jcalvinowens commented Feb 18, 2025

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:

echo 1048576 > /proc/sys/vm/max_map_count

To make it permanent, add this to /etc/sysctl.conf:

vm.max_map_count = 1048576

@stu-spp
Copy link

stu-spp commented Mar 5, 2025

I was running into this problem too. Increasing the vm.max_map_count to 1048576 fixed it for me. Thank you!!!

@MaxIhlenfeldt
Copy link
Collaborator

Thanks for finding the fix!

@MaxIhlenfeldt MaxIhlenfeldt marked this as a duplicate of #881 Apr 2, 2025
BasketsAlaaf added a commit to BasketsAlaaf/meta-browser that referenced this issue Apr 2, 2025
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]>
BasketsAlaaf added a commit to BasketsAlaaf/meta-browser that referenced this issue Apr 2, 2025
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]>
BasketsAlaaf added a commit to BasketsAlaaf/meta-browser that referenced this issue Apr 3, 2025
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]>
BasketsAlaaf added a commit to BasketsAlaaf/meta-browser that referenced this issue Apr 3, 2025
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants