Chrome can't view jobs
Summary
In the past, I was able to view the JOB page without lag.
Since a recent update of Gitlab, I can't tell you exactly which one, then this page started to get super slow, I can say almost unusable except with patience and many refresh
Steps to reproduce
Start a long job on any projects and go to /jobs/$jobId
What is the current bug behavior?
Scrolling can be stuck, the whole page frozen, selection of text can take forever
What is the expected correct behavior?
I expect the job page to be fluid
Results of GitLab environment info
Expand for output related to GitLab environment info
root@git:/# gitlab-rake gitlab:env:infoSystem information System: Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.3 Redis Version: 3.2.12 Git Version: 2.22.2 Sidekiq Version:5.2.7 Go Version: unknown
GitLab information Version: 12.5.4 Revision: 63af04cacf5 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.9 URL: https://git.kopaxgroup.com HTTP Clone URL: https://git.kopaxgroup.com/some-group/some-project.git SSH Clone URL: ssh://git@git.kopaxgroup.com:20022/some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers:
GitLab Shell Version: 10.2.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
root@git:/# gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ...Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 10.2.0 ? ... OK (10.2.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Checking Reply by email ...
IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped
Checking Reply by email ... Finished
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 8 users of 100 limit.
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 3/1 ... yes 3/2 ... yes 3/4 ... yes 3/7 ... yes 3/8 ... yes 3/10 ... yes 3/23 ... yes 3/24 ... yes 3/25 ... yes 11/33 ... yes 12/34 ... yes 3/35 ... yes 3/47 ... yes 3/48 ... yes 3/54 ... yes 3/60 ... yes 3/63 ... yes 2/64 ... yes 3/65 ... yes 3/66 ... yes 3/67 ... yes 3/69 ... yes 18/71 ... yes 18/72 ... yes 3/73 ... yes 2/74 ... yes 3/75 ... yes 19/76 ... yes 21/78 ... yes 3/82 ... yes 24/83 ... yes 18/84 ... yes 16/85 ... yes 18/86 ... yes 25/87 ... yes 18/88 ... yes 3/89 ... yes 25/90 ... yes 25/91 ... yes 25/100 ... yes 25/101 ... yes 18/102 ... yes 17/105 ... yes 17/107 ... yes 17/108 ... yes 3/110 ... yes 27/111 ... yes 3/112 ... yes 25/114 ... yes 27/115 ... yes 27/116 ... yes 3/117 ... yes 29/118 ... yes 25/119 ... yes 25/120 ... yes 26/121 ... yes 27/122 ... yes 3/124 ... yes 2/125 ... yes 3/126 ... yes 3/127 ... yes 18/129 ... yes 3/132 ... yes 35/133 ... yes 31/134 ... yes 31/135 ... yes 31/136 ... yes 31/137 ... yes 3/138 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.3) Git version >= 2.22.0 ? ... yes (2.22.2) Git user has default SSH configuration? ... yes Active users: ... 10 Is authorized keys file accessible? ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
I have no clue. I am using gitlab everyday and I saw this regression and tought at the time, that you will obviously fix it, after a few major release, it is not fixed so I am worrying a bit..