"Stages" view consumes 100% of CPU sometimes, even with nothing going on

[efip-ns]

Jenkins and plugins versions report

Environment

I used https://ci.jenkins.io/job/Reporting/job/deprecated-usage-in-plugins/multi-pipeline-graph/  

What Operating System are you using (both controller, and any agents involved in the problem)?

I used https://ci.jenkins.io/job/Reporting/job/deprecated-usage-in-plugins/multi-pipeline-graph/ which is publicly available.

My client is Chrome 125 and Safari 18.6 on MacOS Sequoia 15.6, but I also observed it with Chrome 125 on Linux.

Reproduction steps

1. Step 1: Open Chrome or Safari.
2. Step 2: Go to https://ci.jenkins.io/job/Reporting/job/deprecated-usage-in-plugins/multi-pipeline-graph/
3. Step 3: Open Chrome's "Task Manager".

Expected Results

I would expect the page to not be stuck.

Actual Results

The page is stuck and frequently pops "Page has become unresponsive" prompt from Chrome.

Anything else?

Seems to happen consistently on several machines and not happen at all on several others.

Seems to be a blocker to #791.

Are you interested in contributing a fix?

No response

[felipecrs]

I don't think Chrome 125 is within the supported range. Can you please test with a newer version?

https://www.jenkins.io/doc/book/platform-information/support-policy-web-browsers/#browser-compatibility-matrix

[timja]

I can't reproduce on Chrome 139 macOS or Safari 18.6 on Sequoia.

[efip-ns]

It would take me some time to get Chrome updated on that machine (it's connected to a TV and I have no admin privileges there), I'll report back.

P.S. This (obviously) didn't start while I was observing jenkins.io, but rather two of my pipelines' stages view; I however noticed that this reproduces on the public page as well.

[lewisbirks]

This is probably due to the DurationFormat polyfill used here.

We have had a few reports from people on older browsers saying that the polyfill impacts performance and Mozilla states that the minimum supported version of Chrome with the feature implemented is Chrome 129.

[efip-ns]

The upgrade to Chrome 139 improved things a bit, however this is still at a level I personally find quite uncomfortable (50% CPU for a tab with one running job, 92% CPU for a tab with two.)

The machine is Intel i7 6-core with 8GB RAM, while neither a "monster" nor a "beast" in 2025, I would expect it to be quite adequate if all it does is running Chrome with 3 tabs.

Screenshot

[felipecrs]

The problem is that being unable to reproduce it.

[timja]

I wonder if we should just remove the polyfill and just don't display the timing if not supported?