Calling the build history of an agent causes blocked threads, doesn't give any reply to the user in the UI.

We experienced this problem lately when a user wanted to see the "Build History" of the agent that he manages. The UI of this build history does not show anything, only a thin progress bar, which is hardly to be recognized and it shows a little pop up on hovering

The user thought that there is no progress at all and refreshed the call multiple times. This lead to a lot of threads that get stuck / blocked: -> those threads all seem to call the same logic again and again. From my POV it shouldn't, the logic should detect if the same call is already being processed in the background.

Next to that we saw some "Timer" threads being blocked as well:

It took Jenkins some hours to finalize the threads, I can just guess that all of them crawl the file system to find fitting builds, but not sure what happens in the background.

I would expect that Jenkins is capable to deny a recreation of the same thread over and over again. Maybe this has been solved already in a newer Jenkins version, but I could not find a related ticket.