Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

`java.lang.OutOfMemoryError: Java heap space` on test-mnx-ubuntu2204-x64-2

Aberta
  • Algo errado?
#4,538 4 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
38/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
git, java
Domínio
ci-cd, infrastructure

Direção de pesquisa

Start with the two linked node-cross-compile build logs and compare them with the successful builds on test-mnx-ubuntu2204-x64-2 between those failures. Trace the checkout path shown in the stack trace through Jenkins Git and remoting; the payload does not identify repository files or tests. Done means explaining the intermittent heap exhaustion and providing a verified fix or actionable infrastructure change.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

incident

Two node-cross-compile runs have failed on test-mnx-ubuntu2204-x64-2 with OutOfMemoryError during git checkout:

e.g.

12:07:42  > git checkout -f c7dfcaba79481d29170b9d48f409e89197787ba4 # timeout=10
12:08:04 FATAL: Self-suppression not permitted
12:08:04 java.lang.OutOfMemoryError: Java heap space
12:08:04 Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 8.225.232.44/8.225.232.44:43584
12:08:04 		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1916)
12:08:04 		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:384)
12:08:04 		at hudson.remoting.Channel.call(Channel.java:1108)
12:08:04 		at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:306)
12:08:04 		at PluginClassLoader for git-client/jdk.proxy72/jdk.proxy72.$Proxy147.withRepository(Unknown Source)
12:08:04 		at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:264)
12:08:04 		at PluginClassLoader for git//hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1428)
12:08:04 		at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1368)
12:08:04 		at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
12:08:04 		at hudson.scm.SCM.checkout(SCM.java:540)
12:08:04 		at hudson.model.AbstractProject.checkout(AbstractProject.java:1254)
12:08:04 		at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:648)
12:08:04 		at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:84)
12:08:04 		at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521)
12:08:04 		at hudson.model.Run.execute(Run.java:1849)
12:08:04 		at PluginClassLoader for matrix-project//hudson.matrix.MatrixBuild.run(MatrixBuild.java:331)
12:08:04 		at hudson.model.ResourceController.execute(ResourceController.java:97)
12:08:04 		at hudson.model.Executor.run(Executor.java:456)
12:08:04 Caused: java.lang.IllegalArgumentException: Self-suppression not permitted
12:08:04 	at java.base/java.lang.Throwable.addSuppressed(Throwable.java:1101)
12:08:04 	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:27)
12:08:04 	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:83)
12:08:04 	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
12:08:04 	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
12:08:04 	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:986)
12:08:04 	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:961)
12:08:04 	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:907)
12:08:04 	at hudson.remoting.UserRequest.perform(UserRequest.java:225)
12:08:04 	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
12:08:04 	at hudson.remoting.Request$2.run(Request.java:391)
12:08:04 	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:81)
12:08:04 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:328)
12:08:04 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
12:08:04 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
12:08:04 	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:312)
12:08:04 	at java.base/java.lang.Thread.run(Thread.java:1474)

It's not consistent though -- other builds on the same machine in between those two succeeded.

Image
Linguagem predominante
Jinja
Estrelas
544
Forks
184
Merge médio
4d 16h
PRs com merge (30d)
12

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nodejs/build

Todas as issues de nodejs/build

Issues semelhantes

Mais issues de DevOps

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.