Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-68210

Call to any Step triggers Garbage Collector OutOfMemoryError


      I have two Jenkins servers. I updated a bunch of plugins on both yesterday. I believe a key one was Pipeline: Model APIVersion2.2075.vce74e77b_ce40

      After that all runs using agents launched by Amazon EC2 plugin
      Version1.68 would cause the error:

      java.lang.OutOfMemoryError: GC overhead limit exceeded

      Reverting from Pipeline Version2.7 to 2.6 and the error is no longer happening. No other changes were applied.

      Here's an example of the full error:

      java.lang.OutOfMemoryError: GC overhead limit exceeded
      Caused: java.io.IOException: Remote call on EC2 (AWS Dev Account) - Pacific Builder (i-00d8bd6e0c699d7dc) failed
      at hudson.remoting.Channel.call(Channel.java:1004)
      at hudson.FilePath.act(FilePath.java:1194)
      at hudson.FilePath.act(FilePath.java:1183)
      at hudson.FilePath.mkdirs(FilePath.java:1374)
      at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:97)
      at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71)
      at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      at java.lang.Thread.run(Thread.java:748)
      Finished: FAILURE

      In the comments I'll list out the plugins and versions of the working system and the failing system

            Unassigned Unassigned
            geoff Geoff Dunn
            0 Vote for this issue
            1 Start watching this issue