Bug #22754
open
3.1.0 workbench workflow page extreme slowness
Added by Ivan Diaz Alvarez 14 days ago.
Updated 2 days ago.
Description
Since ver 3.1.0, workflow pages tab in chrome exhibit hangs and get stuck:
- This is mainly CPU based, checked the memory consumption, but it was normal (in this case, for this ticket)
Doesn't seem related to cluster size or wokflog / log size
- It tends to happen when the logs / outputs are empty, specially when seting up basic compute on the upgrade so that workflows failed and having no logs was triggered.
- closing the tab and opening other with the same url solves the issue momentarily, but it crops again after some minutes.
Attached image with elevated cpu consumption in chrome
Files
Forgot to add the page gets unresponsive in this condition
- Assigned To set to Stephen Smith
- Category set to Workbench2
- Target version set to Development 2025-04-16
I am also seeing this in Firefox 137. The most reliable way to see it seems to be to start a non-trivial workflow and then leave a browser tab open on the workflow process page. You can tab away but for me when I hear my laptop fan kick in that tells me the tab has wedged itself and needs to be stopped.
Ivan confirmed in a meeting that this is seen on queued/running workflows, not completed-and-failed ones. In his particular case, the user was monitoring a workflow that was impossible to dispatch, so it was stuck in the queued state.
- Target version changed from Development 2025-04-16 to Development 2025-04-30
In the "queued" state, it polls for container status. This may have some unreasonable resource leak.
In the "running" state, it collects runtime logs. This also may have some unreasonable resource leak, but the polling mechanism for logs is different from the polling mechanism for container status used in the "queued" state.
I suggest the following tests to reproduce/diagnose the problem:
- Leave the browser on a page in "Queued" state for several minutes with the javascript profiler active.
- Leave the browser on a page in "Running" state for several minutes with the javascript profiler active.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 