updateBuildHistory in hudson-behavior.js very expensive on large build histories

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I just upgraded to 1.123, and I am having problems with build pages that contain
      a lot of builds (one example has 650 builds).
      In revision 1.27 of main/war/resources/scripts/hudson-behavior.js was added a
      line of code that adds behavior during the updateBuildHistory ajax call. I don't
      know exactly what this does, but looking in the debugger it iterates through the
      DOM tree returned by hudson when the page asks for the new build history. In my
      case this is huge, and prototype goes into several tight loops with over 3000
      elements.

      On my (pretty good) computer (core 2 duo under linux, firefox), this results in
      3-4second freeze (with one of the cores maxed out at 100%) and eventually
      firefox asks if it should kill the thread...

      Is the behavior needed? it worked fine on 1.102 (the previous revision I was
      running).

            Assignee:
            Unassigned
            Reporter:
            bruyeron
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: