You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[JENKINS-56377] console log hangs in web browser after upgrade #681
We recently upgraded Jenkins from 2.89.4 to 2.150.3 and then upgraded the workflow-job plugin from 2.25 to 2.31 and are now seeing an issue where the full console log in the Jenkins UI is having issues loading. We run a parallel pipeline heavy workload which results in a 13mb console log in 2.150.3 and a 46mb console log in 2.89.4. In Jenkins 2.89.4, it took 45 seconds to load the full console log file in Chrome and even less time in Firefox. In Jenkins 2.150.3 the log file took 2m 30sec in Chrome and after 5 minutes never loaded in Firefox. I kept seeing "A web page is slowing down your browser. What would you like to do? [Stop It, Wait]" and eventually Firefox became unresponsive. I used Chrome 72 and Firefox 65 in my testing.
We recently upgraded Jenkins from 2.89.4 to 2.150.3 and then upgraded the workflow-job plugin from 2.25 to 2.31 and are now seeing an issue where the full console log in the Jenkins UI is having issues loading. We run a parallel pipeline heavy workload which results in a 13mb console log in 2.150.3 and a 46mb console log in 2.89.4. In Jenkins 2.89.4, it took 45 seconds to load the full console log file in Chrome and even less time in Firefox. In Jenkins 2.150.3 the log file took 2m 30sec in Chrome and after 5 minutes never loaded in Firefox. I kept seeing "A web page is slowing down your browser. What would you like to do? [Stop It, Wait]" and eventually Firefox became unresponsive. I used Chrome 72 and Firefox 65 in my testing.
I have been looking into related log performance issues, and I noticed that large logs were very slow in Chrome. In particular, Chrome would hang when scrolling, and show just a blank page until it became responsive again, and selecting text was very delayed. Firefox did not have the same issue. I think the issue was at least partly caused by this bug in Chromium, which was just marked as fixed yesterday. I was able to verify that updating Chrome to a version with the fix for that issue (79.0.3945.130) caused the issues I was experiencing to go away, and for performance to be much closer to Firefox.
Are other users seeing this problem on Firefox, or only in Chrome/Chromium?
They are definitely some other things that should be improved, I just wanted to note that at least some of the problem seems to have been a bug in Chromium that was very recently fixed.
I have been looking into related log performance issues, and I noticed that large logs were very slow in Chrome. In particular, Chrome would hang when scrolling, and show just a blank page until it became responsive again, and selecting text was very delayed. Firefox did not have the same issue. I think the issue was at least partly caused by this bug in Chromium, which was just marked as fixed yesterday. I was able to verify that updating Chrome to a version with the fix for that issue (79.0.3945.130) caused the issues I was experiencing to go away, and for performance to be much closer to Firefox.
Are other users seeing this problem on Firefox, or only in Chrome/Chromium?
They are definitely some other things that should be improved, I just wanted to note that at least some of the problem seems to have been a bug in Chromium that was very recently fixed.
Oleg Nenashev I am currently working on this and I am making good progress. Logs that used to load for 2 minutes now load in the span of 2-5 seconds. Will make a pull request on Tuesday.
Oleg Nenashev I am currently working on this and I am making good progress. Logs that used to load for 2 minutes now load in the span of 2-5 seconds. Will make a pull request on Tuesday.
My PR build failed, and my guess is that the tests require a higher version of Jenkins (all of them pass locally). This is the error:
Caused by: java.io.IOException: Pipeline: Nodes and Processes version 2.35 failed to load.
- You must update Jenkins from version 2.164.1 to version 2.176.1 or later to run this plugin.
The last commit in the main repository seems to be related to the build process (and also updated the required Jenkins version). I am not 100% sure if that is the reason though.
My PR build failed, and my guess is that the tests require a higher version of Jenkins (all of them pass locally). This is the error:
Caused by: java.io.IOException: Pipeline: Nodes and Processes version 2.35 failed to load.
- You must update Jenkins from version 2.164.1 to version 2.176.1 or later to run this plugin.
The last commit in the main repository seems to be related to the build process (and also updated the required Jenkins version). I am not 100% sure if that is the reason though.
Activity
jenkins-infra-bot commentedon Dec 6, 2019
fengxx:
Raw content of original comment:
I think it is because the javascript function which loops each line and appended parallel label
https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/workflow/job/console/NewNodeConsoleNote/script.js#L21-L42
It can be reproduced by a generating lots of lines in parallel step, such as
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)}The consoleFull is very slow and firefox complaining about the js
jglick does it make sense to generate the label in backend(Jenkins side) ?
jenkins-infra-bot commentedon Dec 6, 2019
Raw content of original comment:
I would start by seeing if the loop can be cut off at some threshold, then see if the loop can be optimized for the lines it does process.
jenkins-infra-bot commentedon Jan 23, 2020
Raw content of original comment:
I have been looking into related log performance issues, and I noticed that large logs were very slow in Chrome. In particular, Chrome would hang when scrolling, and show just a blank page until it became responsive again, and selecting text was very delayed. Firefox did not have the same issue. I think the issue was at least partly caused by this bug in Chromium, which was just marked as fixed yesterday. I was able to verify that updating Chrome to a version with the fix for that issue (79.0.3945.130) caused the issues I was experiencing to go away, and for performance to be much closer to Firefox.
Are other users seeing this problem on Firefox, or only in Chrome/Chromium?
They are definitely some other things that should be improved, I just wanted to note that at least some of the problem seems to have been a bug in Chromium that was very recently fixed.
jenkins-infra-bot commentedon Feb 21, 2020
sundarkasturi_boa:
Raw content of original comment:
We are facing the same issue.. Chrome does not respond or return back on a large console log
Any idea when this would be resolved? Seems open from about a year.
jenkins-infra-bot commentedon May 15, 2020
Raw content of original comment:
FYI jhartley. It looks like something UX SIG might be interested in.
jenkins-infra-bot commentedon May 15, 2020
jhartley:
Raw content of original comment:
duemir - this doesn't really fit the work the UX SIG is currently engaged with. Thanks for letting me know though
jenkins-infra-bot commentedon May 24, 2020
Raw content of original comment:
gerganzh is it something you are working on?
jenkins-infra-bot commentedon May 24, 2020
Raw content of original comment:
Oleg Nenashev I am currently working on this and I am making good progress. Logs that used to load for 2 minutes now load in the span of 2-5 seconds. Will make a pull request on Tuesday.
jenkins-infra-bot commentedon May 26, 2020
Raw content of original comment:
I've made a pull request: #164
My PR build failed, and my guess is that the tests require a higher version of Jenkins (all of them pass locally). This is the error:
Caused by: java.io.IOException: Pipeline: Nodes and Processes version 2.35 failed to load. - You must update Jenkins from version 2.164.1 to version 2.176.1 or later to run this plugin.The last commit in the main repository seems to be related to the build process (and also updated the required Jenkins version). I am not 100% sure if that is the reason though.
jenkins-infra-bot commentedon Feb 3, 2022
jessejoe:
Raw content of original comment:
I believe I've narrowed down the cause of this slowness (but not a fix), please see my comments in https://issue-redirect.jenkins.io/issue/62241
EDIT: looks like the PR above may be addressing this, I glossed right over it!
jenkins-infra-bot commentedon Dec 12, 2025
[Original
is_duplicated_byfrom Jira: JENKINS-62241]