-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 2.222.3
workflow-job-plugin 2.39
In the latest Jenkins version and workflow-job-plugin, it seems that the jenkins console log is frozen. I've tested both Firefox 76 and Chromium 81.0.4044.129.
From trying to debug this issue, it seems that it is related to the workflow-job-plugin. It seems to be stuck processing nodes from the console:
I've downgraded the plugin to version 2.36 - it seems that is the last version that works.
When upgrading to 2.37, the console log freezes the tab again.
This is the test job I ran to generate the console output:
def genText(lines){ (1..lines).each{ println "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur interdum fringilla interdum" } return true }parallel "branch-1" : { genText(20000) }, "branch-2": { genText(20000)}
- duplicates
-
JENKINS-56377 console log hangs in web browser after upgrade
-
- In Progress
-
[JENKINS-62241] Console freezes tab for chrome & firefox
Summary | Original: Console freezes tab | New: Console freezes tab for chrome & firefox |
Description |
Original:
In the latest Jenkins version and workflow-job-plugin, it seems that the jenkins console log is frozen. From trying to debug this issue, it seems that it is related to the workflow-job-plugin. It seems to be stuck processing nodes from the console: !screen_shot_2020-05-10_at_11.55.33.png|width=592,height=51! I've downgraded the plugin to version 2.36 - it seems that is the last version that works. When upgrading to 2.37, the console log freezes the tab again. This is the test job I ran to generate the console output: {code:java} def genText(lines){ (1..lines).each{ println "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur interdum fringilla interdum" } return true }parallel "branch-1" : { genText(20000) }, "branch-2": { genText(20000)} {code} |
New:
In the latest Jenkins version and workflow-job-plugin, it seems that the jenkins console log is frozen. I've tested both Firefox 76 and Chromium 81.0.4044.129. From trying to debug this issue, it seems that it is related to the workflow-job-plugin. It seems to be stuck processing nodes from the console: !screen_shot_2020-05-10_at_11.55.33.png|width=592,height=51! I've downgraded the plugin to version 2.36 - it seems that is the last version that works. When upgrading to 2.37, the console log freezes the tab again. This is the test job I ran to generate the console output: {code:java} def genText(lines){ (1..lines).each{ println "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur interdum fringilla interdum" } return true }parallel "branch-1" : { genText(20000) }, "branch-2": { genText(20000)} {code} |
Attachment | New: workflow-job.png [ 57187 ] |
Attachment | New: image-2022-02-01-14-19-00-775.png [ 57188 ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Link | New: This issue duplicates JENKINS-56377 [ JENKINS-56377 ] |
I am also hitting this issue when any of our pipelines has more than a few hundred KB of log. This is occurring for us on a brand new Jenkins server running the current LTS version 2.319.2 and the current Pipeline: Job plugin. Loading /console hangs for multiple minutes in the browser giving a warning about javascript: "This page is slowing down Firefox, stop this page?" When disabling javascript on the page, /console loads instantly for the build. Further debugging in the Jenkins Gitter channel with some Javascript profiling in Chrome I was also able to see org.jenkinsci.plugins.workflow.job.console.NewNodeConsoleNote/script.js:1 as being the likely culprit:
After finding this ticket, I also downgraded workflow-job from the current version (1145.v7f2433caa07f) to 2.36 and the issue no longer occurs, /console loads quickly. Upgrading just 1 minor release to 2.37 and the issue occurs again, so it seems like there was a change between 2.36 and 2.37 causing this. I'm not sure where the source for these releases are since the current source in Github starts at release 2.41.
I'm bumping this to Major since in our experience we can't load the console for any of our builds without the browser hanging, disabling javascript, or going to /consoleText and this occurs with the latest version of the plugin and the latest LTS jenkins release.
Here's some additional profiling of the page if it's helpful: