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

Pipeline job is failed with java.lang.StackOverflowError

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: pipeline
    • Environment:
      Jenkins Master WIndows Server 2012, Jenkins
      version 2.112, 2 slaves, Jenkins Slave Windows 10 and Jenkins Slave Debian 9.3(Stretch)
    • Similar Issues:

      Description

      We use Multi branch job. Sometimes pipeline job is failed with java.lang.StackOverflowError.I send you our Jenkinsfile and pipeline.log. Maybe is job name too long?

      Also sometimes parallel stages hang when one stage is failed(failFast true) via this exception but I think it's other bug. Please write if you need some additional logs or system information.

      Jenkinsfile

      log.txt

        Attachments

        1. 111.zip
          228 kB
        2. autoloader.zip
          31 kB
        3. Jenkinsfile
          6 kB
        4. log.txt
          263 kB
        5. utils.groovy
          5 kB

          Activity

          Hide
          based3 Basile Chandesris added a comment - - edited

          I also got this, while playing with environment variables (bindings) and pipeline/workflow environment section.

          java.lang.StackOverflowError
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:498)
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503)
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503)
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503)
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503)
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503)
          at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503)

          Jenkins 2.190.1, lastest plugin updates,  multibranch, GNU/LInux.

           

           

          Show
          based3 Basile Chandesris added a comment - - edited I also got this, while playing with environment variables (bindings) and pipeline/workflow environment section. java.lang.StackOverflowError at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:498) at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503) at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503) at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503) at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503) at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503) at org.jenkinsci.plugins.workflow.cps.DSL.flattenGString(DSL.java:503) Jenkins 2.190.1, lastest plugin updates,  multibranch, GNU/LInux.    
          Hide
          erikpaulmiller Erik Miller added a comment -

          Happening for me as well. Update?

          Show
          erikpaulmiller Erik Miller added a comment - Happening for me as well. Update?
          Hide
          abayer Andrew Bayer added a comment -

          Any update from your side, Aleksandr Gamoskin?

          Show
          abayer Andrew Bayer added a comment - Any update from your side, Aleksandr Gamoskin ?
          Hide
          abayer Andrew Bayer added a comment -

          Ok, if it's not happening when you're not in parallel, then it's got to be something that's temporarily/briefly exposed in one of the parallel branches that Pipeline attempts to serialize when it reaches a safepoint on one of the other branches. Could be Gitea, could be something else - I really can't tell. The best I can advise is that you try to reproduce this as minimally as possible - starting with empty parallel branches and gradually adding bits and pieces until you can reproduce the error.

          Show
          abayer Andrew Bayer added a comment - Ok, if it's not happening when you're not in parallel, then it's got to be something that's temporarily/briefly exposed in one of the parallel branches that Pipeline attempts to serialize when it reaches a safepoint on one of the other branches. Could be Gitea, could be something else - I really can't tell. The best I can advise is that you try to reproduce this as minimally as possible - starting with empty parallel branches and gradually adding bits and pieces until you can reproduce the error.
          Hide
          olecsys Aleksandr Gamoskin added a comment -

          Andrew Bayer I've remove parallel stages and problem does not occur for now. If you need I could send you new groovy files and pipeline.

          Show
          olecsys Aleksandr Gamoskin added a comment - Andrew Bayer I've remove parallel stages and problem does not occur for now. If you need I could send you new groovy files and pipeline.

            People

            • Assignee:
              Unassigned
              Reporter:
              olecsys Aleksandr Gamoskin
            • Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated: