-
Bug
-
Resolution: Unresolved
-
Minor
-
The jenkins server we are using is here:
http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/
My clients are Firefox 52.0 (64-bit) and Chromium 57.0.2987.110 (64-bit) on linux
Problem
When looking at the activity view when there are lots of jobs running the page will eventually lockup.
Steps to Reproduce
This will setup a job that will run all the time, one instance of the job after the next.
This is the pipeline script I was using but I am fairly sure that it doesn't matter all that much what the job is doing other than for timing:
stage('one') { echo 'step one' } stage('two') { echo 'step two' } stage('three') { sleep 1 echo 'step three' } stage('four') { echo 'step four' }
Next go to the Blue Ocean activity view and wait for a few minutes. (This goes very fast if you remove the sleep.)
After those few minutes your browser window should stop responding... And you may see that the browser process is using up a large amount of CPU time.
Notes
I can split this up into three tickets if you guys want. I am not sure how related they are at this point.
When I slowed down the job run time with the above sleep the page still locked up which seems to imply a problem with the number of items not the rate that the items are updating.
When I slowed down the job I also noticed that the top line item's time kept increasing even though the reported time for the job when it finished was constant.
Finally, I noticed that there was a non-zero rate of jobs failing to update in BO. This may be related to the above issue or it could be that the number of jobs run surfaces the issue. Here is a screen cap of the issue in the UI:
I was able to reproduce this. Looking at the browser memory usage it seems that the data collected is never being purged when it reached a certain threshold.