Gitea doesn't open more than 5 tabs in browser

[lakostin]

• Gitea version (or commit ref):
  1.12.0
• Git version:
  2.17.1
• Operating system:
  Ubuntu 18.04.3 LTS
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

I open pull request with multiple commits, then i open 5 new tabs in browser with each commit. Everything is ok. When i open the sixth tab and further they hang with message "Waiting for available socket..." until i close one of the previously opened tabs.
It can be reproduced in any browser.
What can this be connected to?

Screenshots

[lunny]

can't reproduce in https://gitea.com

[lakostin]

Updated description.

[wkobiela]

@lakostin
Just checked myself, Gitea 1.12.0, GIT 2.26.2, MySQL, hosted on Synology.
Created PR with >5 commits, opened PR and each commit multiple times. No issues.

[lakostin]

I have this isssue on multiple instances and even on different versions. All served by docker btw

[chxseh]

Can confirm, opening any new tabs after 6 have loaded for me results in awaiting for socket. Hosting on Docker as well.

[dexterxx-pl]

I had same issue here, just after updating to v1.12.
It's not related just to PR's - in my case I've just opened new tabs of issues of my project - loading just stucks... and it stucks for many minutes.

CPU usage stays at typical level, logs shows that database (MySQL in my case) also respond in typical time.

Now I've just figured out, that restarting gitea didn't solved problem, but restarting proxy (apache2) does.

After restarting I cannot now reproduce it 👎

@lakostin are you using proxy at front of gitea?

[chxseh]

@dexterxx-pl Tried restarting my proxy in front of gitea to no effect.

[lafriks]

I think it is related to events endpoint that uses sockets for getting events about new notifications. We should probably somehow limit sockets count per user probably

[deptyped]

Same problem. But I could not reproduce this issue without a reverse proxy server (nginx in my case).
By the way, in Firefox pages stop loading after five clicks on the site in one tab.

UPD: Using http2 in nginx solved the problem

[zeripath]

Yeah I suspect this is EventSource issues.

[zeripath]

So I don't think this is the server holding things up but rather the browser. It looks like Firefox is blocking instead of just failing out.

[confusedsushi]

I can confirm this. It happened first after upgrading to 1.12. I am running gitea on Windows 10 2004 with an apache reverse proxy on Ubuntu 18.04.

I am able to reproduce this with Firefox and Chrome.