Skip to content

[JENKINS-56377] console log hangs in web browser after upgrade #681

Open

Description

@jenkins-infra-bot

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.


Originally reported by mkozell, imported from: console log hangs in web browser after upgrade
  • assignee: gerganzh
  • status: In Progress
  • priority: Minor
  • component(s): workflow-job-plugin
  • label(s): performance, pipeline
  • resolution: Unresolved
  • votes: 2
  • watchers: 14
  • imported: 20251212-090250
Raw content of original issue

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.

environment
Jenkins v2.89.4 w/ workflow-job-plugin v2.25<br/>
Jenkins v2.150.3 w/ workflow-job-plugin v2.31<br/>
Jenkins v2.289.2 w/ workflow-job-plugin v2.41

Activity

  1. jenkins-infra-bot commented on Dec 6, 2019

    @jenkins-infra-bot
    Author
    fengxx:

    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) ?

  2. jenkins-infra-bot commented on Dec 6, 2019

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • 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.

    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.

  3. jenkins-infra-bot commented on Jan 23, 2020

    @jenkins-infra-bot
    Author
    dnusbaum:
    • Original comment link
    • 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.

    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.

  4. jenkins-infra-bot commented on Feb 21, 2020

    @jenkins-infra-bot
    Author
    sundarkasturi_boa:
    • Original comment link
    • 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.

    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.

  5. jenkins-infra-bot commented on May 15, 2020

    @jenkins-infra-bot
    Author
    duemir:
    • Original comment link
    • Raw content of original comment:

      FYI jhartley. It looks like something UX SIG might be interested in.

    FYI jhartley. It looks like something UX SIG might be interested in.

  6. jenkins-infra-bot commented on May 15, 2020

    @jenkins-infra-bot
    Author
    jhartley:
    • Original comment link
    • 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

    duemir - this doesn't really fit the work the UX SIG is currently engaged with. Thanks for letting me know though

  7. jenkins-infra-bot commented on May 24, 2020

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

      gerganzh is it something you are working on?

    gerganzh is it something you are working on?

  8. jenkins-infra-bot commented on May 24, 2020

    @jenkins-infra-bot
    Author
    gerganzh:
    • Original comment link
    • 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. 

    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. 

  9. jenkins-infra-bot commented on May 26, 2020

    @jenkins-infra-bot
    Author
    gerganzh:
    • Original comment link
    • Raw content of original comment:

      I've made a pull request: Fix issue with big logs, causing the browser to freeze (JENKINS-56377) #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.

    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.

  10. jenkins-infra-bot commented on Feb 3, 2022

    @jenkins-infra-bot
    Author
    jessejoe:

    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!

  11. jenkins-infra-bot commented on Dec 12, 2025

    @jenkins-infra-bot
    Author

    [Original is_duplicated_by from Jira: JENKINS-62241]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions