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

OOM error w/ VertexAI native image builds #11368

Open
burkedavison opened this issue Dec 26, 2024 · 2 comments
Open

OOM error w/ VertexAI native image builds #11368

burkedavison opened this issue Dec 26, 2024 · 2 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@burkedavison
Copy link
Member

https://fusion2.corp.google.com/invocations/d49b6be3-bfa7-4285-bbd4-105206b97ec4/targets/cloud-devrel%2Fclient-libraries%2Fjava%2Fgoogle-cloud-java%2Fnightly%2Fgraalvm-sub-jobs%2Fnative-a%2Fgraalvm-native-5;config=default/log

[6/8] Compiling methods...    [***************]                                                        (244.1s @ 5.62GB)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 1789394944 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/src/github/google-cloud-java/hs_err_pid6313.log
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000615280000, 1789394944, 0) failed; error='Not enough space' (errno=12)
@burkedavison burkedavison self-assigned this Dec 26, 2024
@burkedavison
Copy link
Member Author

I've changed the machine pool to cloud-java-graalvm. If we continue to see this OOM error, we can adjust the machine's instance type to increase available memory. See cl/709802858 for more information.

@burkedavison burkedavison added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Dec 26, 2024
@burkedavison
Copy link
Member Author

Reverting pool change, as the current project it runs on doesn't have sufficient quota to run all nightlies in parallel without hitting deadline limits.

@burkedavison burkedavison reopened this Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

1 participant