We have a pipeline that has one job and the job has many builds (36,000 builds).

Attempting to click the job to view the build output returns ERR_EMPTY_RESPONSE in chrome. Looking at Chrome's developer tools, it appears that Chrome is still attempting to get the build output (notice the (pending) in the network logs). Perhaps there is some inefficient query for having a ton of builds for one job?