Research crash/hang after interactive search in multiple tabs (i.e. >6-8) #Sockets #HTTP2

Help & Support
#1

Sonarr version (exact version): 3.0.7.1477 via Docker
Mono version (if Sonarr is not running on Windows): 5.20.1.34
OS: macOS 12.3.1 (21E258)
Debug logs: if relevant then please request
Description of issue: see below

:wave:

Hope you’re well

Thanks for amazing software

Steps to reproduce issue

  1. Open new tab
  2. Visit series
  3. Do an episode interactive search
  4. Repeat steps 1-3

Unexpected behaviour

After about 5 tabs Sonarr’s UI hangs and I lose the ability to load any more Sonarr tabs without restarting the app

Expected behaviour

Do multiple interactive searches for all episodes in a typical season; to complete in the background

Log

I’ve inspected logs but nothing obviously insightful. If relevant then please request.

TODO

If I try to load new Sonarr tabs while it’s, seemingly, crashed then I get the following browser error:

ERR_SOCKET_NOT_CONNECTED

Visiting vivaldi://net-internals/#sockets and “flushing socket pools” immediately fixes things

Is this a Sonarr issue or a browser issue or both, what’s going on and how can it be fixed?

I did think it was because I was using the “all” jackett API call (sorry, I’m lazy right now :weary:) but I tried with a single indexer and exact same issue

Welcome feedback/input

If you have any issues (e.g. questions/queries) then happy to help

Keep up amazing work :kissing_heart:

Hope this helps and to hear back

Sincerely

1 Like
#2

Related:

#3

Browsers limit the number of concurrent connections to a single server, in Chrome last I looked this limit was 3, this applies across different tabs in the browser as well.

With 5+ manual searches going off, each one will open a long term connection to the webserver to wait for results, since you’re exceeding the maximum of 3 the additional requests will be queued by the browser, but the 3 open connections will block any other network request to the Sonarr backend from executing as well, which means new tabs won’t load and any existing tabs won’t be able to navigate to new pages.

It sounds like Vivaldi can’t queue more requests to the Sonarr backend because it’s reached some sort of internal limit mostly due to the long running search requests or the fact that they’re long running is maybe the issue in itself, but the only workaround I can suggest is don’t do what you’re attempting to do.

#9

[…] the only workaround I can suggest is don’t do what you’re attempting to do

LOL

🫡

Cheers

FYI https://superuser.com/questions/499114/how-to-increase-chromes-connections-per-server > https://stackoverflow.com/questions/36835972/is-the-per-host-connection-limit-raised-with-http-2/36847527#36847527

FYI https://web.dev/performance-http2/#request-and-response-multiplexing

FYI https://forum.vivaldi.net/topic/74822/how-does-vivaldi-use-http2

Can anyone running Sonarr on HTTPS emulate my issue?

Hope to hear back

Cheers

Assuming Mono (seems HTTP2 support arrived ~2017) handles Sonarr’s web server stuff, I’m starting to think my issue is fixable with some Docker deployment enhancements (e.g. http > https)…?

#10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.